3 ms·
I hope at some point golang drops its "too complicated" defense against doing more sensible things that aren't _that_ complicated but add a lot of safety. I say
by parhamn 4y ago
I hope at some point golang drops its "too complicated" defense against doing more sensible things that aren't _that_ complicated but add a lot of safety. I say this as someone who loves go and has written A LOT of it.
More and more people will use Rust and Typescript and realize what a joke go's type system is compared to those. But you don't need to go as far as those languages have -- lacking sum types, exhaustive switches, discriminant unions, proper enums, unchecked nils, etc is just lazy. Most reasonably sized software projects end up having some ad-hock crappy workaround to any one of these issues.
After years of waiting for generics. We got the most stunted and simplistic implementation of generics imaginable. You can't even do something as simple function chaining.
- morelisp 4y ago> You can't even do something as simple function chaining. You make this sound like something got lazy about rather than something with major implications for the language semantics/runtime. Serious question: Would you prefer a) the current generics implementation, b) a runtime capable of code generation, c) generics cannot participate in interface implementation, d) some other option?