3 ms·
> Also, devs who use Go and C++ usually have a good reason (embedded systems and such) Just.. drop go from that. Go is closer to JS than to C++/embedded.
by kaba0 3y ago
> Also, devs who use Go and C++ usually have a good reason (embedded systems and such)
Just.. drop go from that. Go is closer to JS than to C++/embedded.
- jdm2212 3y agoGo is great for CLIs and utilities. It compiles to native code, has a low memory footprint, and the source code is pretty readable even if you've never written Go before. And when it crashes you get a human-readable stack trace not just a core dump :) But I've never seen a large-ish Go application that I didn't hate. Because, yeah, as you said, it's closer to JS in a lot of ways.
- kaba0 3y agoI meant it in the way that Go is not cut out for most embedded use cases due to having a fat runtime with GC. It is ok for CLIs and small utilities, but I can’t really stand looking at it (they went with a type syntax that is neither C-like, neither Haskell-like and is absolutely unreadable to me, even though I can usually get the gist of any language from having seen my fair share of syntaxes).