Just Use Go
41–50 of 238 posts
Re: Just Use Go
#42OCaml?
Re: Just Use Go
#43.NET has almost all these upsides, but with a concurrency model (async/await) that is (now) more transferable to other languages.
Re: Just Use Go
#44> The boring choice is the right choice. It always was. Right, absolutely correct, Java is a great choice, so why does this post keep going on about Go?
Re: Just Use Go
#45Go, similar to Rust, has a horrible ecosystem, IMHO. I want to like it, but they already broke backwards compatibility with older systems (try to get the Go compiler running on a slightly older OS X, f.ex.), and for a compiler that's a no-go to me.
Re: Just Use Go
#46Re: Just Use Go
#47With agentic coding you can just use Rust. AI agents are really good at Rust and the good error message the compiler and or borrow checker gives makes it easy for the AI agent to adjust its code and fix it. For non agentic coding Go has terrible error handling. It does not have exceptions or monadic error handling. Some call that a feature but many avoid Go or that specific reason. This will not change because that d…
Re: Just Use Go
#48Also: why can't we vouch for flagged stories now? This post is actually good, and funny, and the conversations are worth having.
Re: Just Use Go
#49Error handling also seems pretty dumb in comparison to Rust. Admittedly Rust is a much more complicated language, but I felt like I could just go learn more Rust instead of bothering with Go and have more fun.