| ▲ | thomascgalvin 6 hours ago | |||||||
I like go, but a lot of little things stop me from loving it. Like, enums. I get a lot out of the box when I use an enum in Java or Kotlin. Converting to/from a String is trivial. Type safety ... exists. I can do that in Go, but I have to hack it in, for every single enum type I want to represent. Enums are not a thing in the language, which means its easier to keep the language in your brain all at once, but at the expense of making it harder to keep the software I'm writing in my head. Is this "enum" the same as that "enum"? I have to go read the code to figure it out. But Go is excellent at a lot of things. Compile times, static binaries, resources compiled right into that binary, execution speed ... there is a lot to love. | ||||||||
| ▲ | nick_ 3 hours ago | parent | next [-] | |||||||
The convention of explicit error handling after every method call is absolutely bonkers to me. I would never use it for anything serious. | ||||||||
| ▲ | ntrianta90 5 hours ago | parent | prev [-] | |||||||
I really wish they had added Enums instead of the stupid generics. | ||||||||
| ||||||||