I'm at this level of agitation because I face a lot of pressure to use Golang even though I feel it negatively impacts some code I want to write. To be told by the community (in some cases the same people), "Leave if you don't like it" and then "You should be here!" is not fun.
-
-
This Tweet is unavailable.
-
Closures in Python are more infuriating than Go generics — they’re surprising. You can’t write a Go program and not know that there aren’t generics; the feature just isn’t there. So: I dispute this vigorously.
1 reply 0 retweets 0 likes -
I’m not arguing that pressure to write in Go is annoying. I would be extremely annoyed if someone pressured me into writing Rust.
1 reply 0 retweets 1 like -
Replying to @tqbf @KirinDave
From my point of view, the problem is that people are now asking for other languages to be like Go, and repeating Go’s problems in new languages. For example, I can make an argument that Go is setting GC progress back a decade.
1 reply 0 retweets 0 likes -
Replying to @pcwalton @KirinDave
Please show me a case where developers are demanding that some other language _not have generics_.
1 reply 0 retweets 1 like -
Replying to @tqbf @KirinDave
Nobody argues to remove features from existing languages. But they do argue that new languages don’t need certain features. 5 years ago I certainly saw a lot of people saying that Go proved that languages don’t need generics: e.g. https://www.reddit.com/r/golang/comments/vldyv/less_is_exponentially_more_rob_pike_on_the/c55vcpr/ …
1 reply 0 retweets 1 like -
Replying to @pcwalton @KirinDave
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".
1 reply 0 retweets 1 like -
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
The tradeoff Go made is the wrong one for most applications. That’s the issue.
-
-
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 - 15 more replies
New conversation -
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.