Re:How generics are implemented in Go 1.18
by dogleash on Wednesday March 02, 2022 @12:29PM
(#30529976)
"The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt." – Rob Pike
[ Parent
| on HN ]
Re:How generics are implemented in Go 1.18
by mnk47 on Wednesday March 02, 2022 @06:17PM
(#30534812)
How many times is this gonna get reposted as some sort of gotcha? He's right, and having to deal with juniors or large teams with varying competence isn't unique to Google. I've met many devs who praise Java for how simple it is to parse through for people of all experience levels (once you get used to the verbosity). In fact, two of Java's founding principles was that it had to be simple and familiar. Yet I don't see anyone pretending that's a bad thing.
Go has the same goals, just a different approach. Java is too verbose, Go takes the simplicity approach too far sometimes. Neither are perfect but they're definitely useful and worth considering for many projects. The fact that it was made with juniors in mind is a plus.
Re:How generics are implemented in Go 1.18
by vmchale on Wednesday March 02, 2022 @08:13PM
(#30535848)
> having to deal with juniors or large teams with varying competence isn't unique to Google.
It's good for "juniors" but not yourself? Lmao.
No one can praise Go without speaking in the third person.