4 ms·
The Go team should have considered generics for Go 1.0 during the 0.x phase. It's 2018. We've done three decades of computer science since C, Oberon, or whatev
by bitwize 8y ago
The Go team should have considered generics for Go 1.0 during the 0.x phase.
It's 2018. We've done three decades of computer science since C, Oberon, or whatever the Go developers drew inspiration from. If you want your language to be taken seriously for large scale app development in the 2010s you need strong static typing, and a sophisticated, parametric type system. No exceptions. Advanced typing constructs like dependent and higher-kinded types are a bonus.
We've also done enough computer science to know there are much better ways to relieve the programmer of the burden of doing all memory/resource management explicitly than a tracing GC. So using a tracing GC in an ostensible systems programming language was another huge boner.
Go 1.x was a cascade of bad decisions. It's like Java was in 1995: a language with training wheels that had to change directions entirely when real programmers started using it to build real applications.
- sethammons 8y ago> No exceptions Well, apparently Go _is_ an exception. It lacks what you point out and is, undeniably, a successful language.
- pjmlp 8y agoHow much would had it achieved if it didn't had the Google logo to go along it? Lets say developed at SV startup XYZ instead.
- giovannibajo1 8y agoThere’s precedent that Google’s brand doesn’t make people magically swallow programming languages without thinking: Dart. I think it’s disingenuous to reduce Go success to some Google marketing operation. I dislike Google as a brand in the way they design products and their weak privacy stance, but I love Go nonetheless.
- xfer 8y agoGo is also similar to languages like limbo/newsqueak. None of those are popular(many might not have even heard of them). So part of success definitely goes to being successfully marketed as a google product.
- pjmlp 8y agoDart suffered from Google politics, trying to take over JavaScript, and then being dropped by Google's own teams (Chrome and Angular). Being rescued by AdWords team, and now having Flutter team as their last hope. Go hasn't suffered from such politics. Let's not forget that Go is a mix of Oberon-2 and Limbo, both a failure regarding market adoption, in spite of their technical qualities.
- sebe 8y agoSome dart ramblings. Seems to me, that the Chrome team is responsible for Dart demise and its later flutter inspired resurgent. Flutter was started by people in the chrome team, as an experimental project called sky. With regards to making it possible to include the dart vm the oilpan project was started. Oilpan, the replacement of reference counting in Blink, with a tracing garbage collector, this would have made it possible for dart vm to sit along side v8 in chrome. Oilpan was started in 2013 and instead of taking months, it took years, I think it finally arrived in 2016. Here is a dart video from io 2013 announcing oilpan. https://youtu.be/huawCRlo9H4 https://youtu.be/huawCRlo9H4
- mcguire 8y agoOr any of the other languages Pike has been involved with?
- nilsocket 8y agoThe main focus of go is to be as simple as possible. It's not that they don't known how to write complicated programs under the hood and keep it simple outside. They want to keep the programming language simple even under the hood where ever possible. Consider implementing a feature in hurry just because many people were asking, one needs to maintain them for the rest of their life even if they hate it so much, because of backward compatibility. It can also be the root cause for many problems. If generics make language complicated, then it's better they don't implement it in the first place.