Things I like about Go (in this order): * useful, not shiny. No new framework every year, just for the sake of it. An actually readable spec. Changes heavily t

Things I like about Go (in this order): * useful, not shiny. No new framework every year, just for the sake of it. An actually readable spec. Changes heavily thought through before being introduced. A programming language isn't a place to move fast and break things, as changes often cannot be undone. * Readable code. You can figure out what a piece of code does pretty easily. Even if you can't do so at first glance, you know where to look next. * Simplicity. I personally like having full understanding of things. This applies both to the language itself, as well as to the tools (go test, go mod, go generate etc). This is pretty subjective. * The formatter. As a screen reader user, aligning things with spaces so that they would form nice little tables is a hard task for me. I'm happy I don't have to do so. * Compiling programs as single, static binaries, assets included. Some small things I don't like (also in that order): * No try macro[1]. IMO try was a better solution than exceptions, and I found the arguments against it not that compelling. * Overrelliance on struct tags, which shouldn't exist at all IMO. I don't want to couple my business logic, storage and view layers. Options for i.e. JSON should be specifiable at call time. * No generics, or, even better, zig-like comptimes. They're simpler and more powerful, though they wouldn't probably neatly fit into go2. Overall, I'd give go about 8.5/10. [1] https://github.com/golang/proposal/blob/master/design/32437-try-builtin.md https://github.com/golang/proposal/blob/master/design/32437-...