Re:Constraints in Go
by cle on Sunday November 17, 2024 @11:48AM
(#42165159)
There are only a handful of things that keep me coming back to Go: fast & simple deployment, good tooling and dependency management, and an excellent stdlib and IO/async abstractions.
Those are all the places I spend all my time in other languages. I really don't care about most of the stuff people complain about that they claim is important (like boilerplate/LoC/error-checking, generics, fancy abstractions, etc.). But doing concurrent stream processing with a mix of IO and CPU blocking in most languages is a freaking nightmare compared to Go.
The one Achilles' heel IMO is not any of the nitpicky type/syntax stuff, it's CGo. That's the one place where I'm always worried that a decision to use Go is going to screw my life up.
Those are all the places I spend all my time in other languages. I really don't care about most of the stuff people complain about that they claim is important (like boilerplate/LoC/error-checking, generics, fancy abstractions, etc.). But doing concurrent stream processing with a mix of IO and CPU blocking in most languages is a freaking nightmare compared to Go.
The one Achilles' heel IMO is not any of the nitpicky type/syntax stuff, it's CGo. That's the one place where I'm always worried that a decision to use Go is going to screw my life up.