Right, I picked my words carefully. I’m asking for any case where there was significant pressure for any language, nascent or otherwise, not to adopt generics. Not “this language we already use that doesn’t have them is OK".
-
-
Replying to @tqbf @KirinDave
I concede that Go’s ideas about generics didn’t catch on outside that particular community. (I’m glad they didn’t!) Exceptions, userspace threading, GC, etc. are another story.
1 reply 0 retweets 1 like -
Replying to @pcwalton @KirinDave
It would be good if people were more up-front about the tradeoff Go makes with its GC, but it is probably not reasonable to say that it’s a bogus tradeoff.
2 replies 0 retweets 1 like -
Replying to @tqbf @KirinDave
The tradeoff Go made is the wrong one for most applications. That’s the issue.
1 reply 0 retweets 1 like -
Replying to @pcwalton @KirinDave
That is a difficult argument to square with empirical observation.
2 replies 0 retweets 2 likes -
Replying to @tqbf @KirinDave
That’s what I’m talking about. Go’s GC benchmarks well, but it is making the wrong tradeoffs. Throughput matters a lot.https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e …
1 reply 0 retweets 3 likes -
Replying to @pcwalton @KirinDave
Yeah, I read that like everyone else. I understand what a generational collector is. The problem with your argument, I think, is that there are much more popular languages with similarly dumb GCs that Go outperforms.
1 reply 0 retweets 1 like -
You want to be arguing that Go’s GC is SUBOPTIMAL. But instead, you’re arguing that it’s INAPPROPRIATE. You’re going to lose that argument.
1 reply 0 retweets 2 likes -
Replying to @tqbf @KirinDave
But I’m only arguing that the Go GC design is suboptimal. I’m not trying to argue that it doesn’t work at all. My problem is that people don’t realize that it’s suboptimal. We’re forgetting all the lessons we learned in the ‘90s, which is tragic.
2 replies 0 retweets 6 likes -
Replying to @pcwalton @KirinDave
There are a lot of good ideas in CS that turn out not to have a whole lot of practical benefit for huge ranges of real-world problems. Look at the instruction set we all code to now! TRAGIC.
2 replies 0 retweets 1 like
Besides, there are real business benefits for x86’s dominance. Not so for Go’s GC. The Go team should have chosen a generational GC. There is no defensible reason why they didn’t.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.