overcyn
Joined 17 years ago
Joined 17 years ago
I have used Go extensively and would disagree with the idea that the lack of generics in go was ill-informed (and therefore a mistake). I find that Go's limited number of features leads to simpler libraries that are much easier to comprehend and use effectively. And in situations where I previously would have reached for generics I am forced to find a different approach and the end result is often better. Yes it does have its drawbacks and is not a perfect solution, but as far as engineering decisions go, I feel it was a successful one.
1. Go doesn't have generics because the authors didn't have strong grasp of type theory.
2. Go doesn't have generics, not from a lack of knowledge, but because the authors' real world software engineering experience had shown to them it wasn't important.
If someone likes driving Corvettes because they think it looks anonymous and non-descript. Who are you to tell them they're wrong. Its their opinion.
https://www.theverge.com/2018/2/7/16984234/how-to-iphone-thr...
https://forums.macrumors.com/threads/iphone-6s-turning-off-a...
https://www.reddit.com/r/apple/comments/4vne2w/does_anyone_e...
And Apple cut the price of battery replacement from $79 -> $29 in response to it.
Why not just advocate for the the corporate world to be more accepting of personal life choices? Firing Kaplan doesn't get you any closer to that.