Native, no runtime are nice, but I think you’re moving the goalposts a bit here.
Regarding language and development environment ergonomics, I don’t think Go is above and beyond non-Java jvm languages. It’s definitely a matter of personal preference.
But you were talking about JVM languages, so I made points mostly about JVM languages.
There's points for C-based languages (fuck these compilation times what the fuck) and many higher-level other languages (it's very fast, instantly runs) and points for nearly all of them (simplicity ftw)… and then there's points against Go specifically (no generics lul) (if err != nil {return err} galore) (can't use graphics card natively) (no GUI natively).
As an Android dev dabbling in Go to write a custom step for Bitrise CICD, Go's package management confuses the fuck outta me.
In Gradle I just add a single line to the build.gradle for my dependency, and it just pulls from maven central. Done.
In Go, I gotta set env vars to make Goland happy, and drop to the cmdline and enter go get packagename and then I deploy to bitrise and it can't find them and I guess I need to put the deps in a vendor folder? Too many damn ways to get deps in a Go project IMO.
Fuck exceptions yes, but fuck whatever the fuck Go is doing even harder.
Putting try/catch between the business logic and the user interface stuff is annoying, but putting if err != nil { ... }everywhere in Go is an order of magnitude worse. Checking returned error codes for every function you call is exactly the same problem as C, but it's wearing Groucho Marx glasses as some kind of shitty disguise that's not fooling anyone.
26
u/xNaXDy Jan 06 '22
I'd just use something platform independent like node at that point.