News for hackers. Stuff that matters.
Re:Why We Switched from Python to Go (2021) by steve_adams_86 on Thursday May 26, 2022 @09:54AM (#31518360)
The last time I was on a team using Go, we ended up ditching it for these reasons.

We realized it took about as much specialization and wheel reinventing as Rust, which offered way better developer ergonomics in ways that mattered to us and wouldn’t panic over things that weren’t easy to predict or caught by the compiler.

There were still tons of trade offs, but it worked well for us. Go is cool but I still can’t seem to figure out where and when I’d prefer it most of all… Especially the poor error handling and lack of safety. These things really drive me crazy.

Re:Why We Switched from Python to Go (2021) by uh_uh on Thursday May 26, 2022 @10:15AM (#31518587)
I prefer Go when I want more safety/performance than Python but less ceremony than Rust.
Re:Why We Switched from Python to Go (2021) by stayfrosty420 on Thursday May 26, 2022 @10:17AM (#31518607)
I think the latter point about "less ceremony" is extremely debatable especially on a larger project.
Re:Why We Switched from Python to Go (2021) by uh_uh on Thursday May 26, 2022 @10:20AM (#31518640)
How does Go have more ceremony than Rust without a borrow checker, lifetime annotations and all?
Re:Why We Switched from Python to Go (2021) by mynegation on Thursday May 26, 2022 @10:39AM (#31518875)
I think the point is not that Rust has less ceremony (it certainly has more), but that you want the “ceremony” for larger scale projects.
Re:Why We Switched from Python to Go (2021) by adolph on Thursday May 26, 2022 @10:37AM (#31518860)
This is why languages like Go offer automatic dynamic memory management, or more simply, garbage collection.

https://medium.com/safetycultureengineering/an-overview-of-m...

Re:Why We Switched from Python to Go (2021) by SideburnsOfDoom on Thursday May 26, 2022 @10:42AM (#31518927)
related, how does having no unit tests have more ceremony than a full test suite?

(and yet it will do so, as you try to find other ways to make your code safe to release)

Re:Why We Switched from Python to Go (2021) by steve_adams_86 on Thursday May 26, 2022 @10:38AM (#31518864)
Fair enough, there are certainly cases where Go is an awesome tool to use.
Re:Why We Switched from Python to Go (2021) by bbkane on Thursday May 26, 2022 @07:48PM (#31524629)
Doesn't Rust also have competing nonstandard ways to handle errors? Right now I think they recommend 3rd party libraries for it (anyhow, one other I don't remember), and those library recommendations have changed over time
Re:Why We Switched from Python to Go (2021) by steve_adams_86 on Thursday May 26, 2022 @08:18PM (#31524807)
I’ve been content with the error handling the language offers, but maybe there are scenarios where it isn’t sufficient that I haven’t encountered.