4 ms·

Please stop. The whole "Go sucks because it doesn't have generics" thing is so overdone at this point. One of Go's strengths is that it's a simple language. It'

by ancarda 10y ago

Please stop. The whole "Go sucks because it doesn't have generics" thing is so overdone at this point. One of Go's strengths is that it's a simple language. It's not getting generics or exceptions anytime soon.

coldtea 10y ago
Well, and I say that one of Go's shortcomings is that it doesn't have generics. See how mere opinions work? Now what?
- ancarda 10y ago
  No there's a difference between expressing an opinion and constantly complaining about it. I already read a hundred comment threads and blog posts for and against generics. Do we really need a "still no generics!" comment on every fucking article about Go? It's just noise at this point. Me pointing out it's a simple language is not a matter of opinion; it's an intentional design decision of Go. Generics will complicate the language more than the Go developers are willing to tolerate. At the time of writing, there's 110 comments on this post and 50 are replies to prodigal_erik's comment on not having generics. HALF the comments on this whole thread are discussing something that's already been discussed for years with no end in sight. For the record, I really don't care if we have generics or not. I just want a higher signal-to-noise ratio for topics about Go on Hacker News. This is a low-signal topic. You may as well argue about systemd.
  - prodigal_erik 10y ago
    I didn't expect a full-blown rehash of my parenthetical. I wanted to point out that "people who use Go today" is one of two audiences who might be interested in announcements of changes.
  - coldtea 10y ago
    >At the time of writing, there's 110 comments on this post and 50 are replies to prodigal_erik's comment on not having generics. HALF the comments on this whole thread are discussing something that's already been discussed for years with no end in sight. Doesn't that point to an actual demand for the feature, and a constant pain point for the language? Why else would it come up in all discussions? It's not about all discussions about Go spin off to random topics / features talk -- it's usually Generics. Similarly, I've not seen people discuss anything else than common pain points (or perceived pain points) in a language. E.g. with Python it will be about the GIL or the 2 to 3 transition. With JS the "fatigue" and/or the crazy coercion rules. With C++ how complicated it is or the slow template system. And so on. Your argument is about ease of use, but people rooting for Generics also argue that they make lots of programming cases easier. Are there many programmers in 2017 really wishing that e.g. C# or Java rather didn't have generics? And what the original feature set as designed isn't very relevant, as languages can and do evolve. Similarly for the opinions of the main developers.
    - ancarda 10y ago
      >Your argument is about ease of use No! My argument is more meta; that this whole discussion is an unproductive waste of time and I can't tell anymore if people are just trolling or looking to start a flame war by bringing up generics in a Go thread. It's noise and it's making Hacker News a worse place. This has been discussed to death already.

by ancarda 10y ago

coldtea 10y ago

Well, and I say that one of Go's shortcomings is that it doesn't have generics. See how mere opinions work? Now what?

ancarda 10y ago
No there's a difference between expressing an opinion and constantly complaining about it. I already read a hundred comment threads and blog posts for and against generics. Do we really need a "still no generics!" comment on every fucking article about Go? It's just noise at this point. Me pointing out it's a simple language is not a matter of opinion; it's an intentional design decision of Go. Generics will complicate the language more than the Go developers are willing to tolerate. At the time of writing, there's 110 comments on this post and 50 are replies to prodigal_erik's comment on not having generics. HALF the comments on this whole thread are discussing something that's already been discussed for years with no end in sight. For the record, I really don't care if we have generics or not. I just want a higher signal-to-noise ratio for topics about Go on Hacker News. This is a low-signal topic. You may as well argue about systemd.
- prodigal_erik 10y ago
  I didn't expect a full-blown rehash of my parenthetical. I wanted to point out that "people who use Go today" is one of two audiences who might be interested in announcements of changes.
- coldtea 10y ago
  >At the time of writing, there's 110 comments on this post and 50 are replies to prodigal_erik's comment on not having generics. HALF the comments on this whole thread are discussing something that's already been discussed for years with no end in sight. Doesn't that point to an actual demand for the feature, and a constant pain point for the language? Why else would it come up in all discussions? It's not about all discussions about Go spin off to random topics / features talk -- it's usually Generics. Similarly, I've not seen people discuss anything else than common pain points (or perceived pain points) in a language. E.g. with Python it will be about the GIL or the 2 to 3 transition. With JS the "fatigue" and/or the crazy coercion rules. With C++ how complicated it is or the slow template system. And so on. Your argument is about ease of use, but people rooting for Generics also argue that they make lots of programming cases easier. Are there many programmers in 2017 really wishing that e.g. C# or Java rather didn't have generics? And what the original feature set as designed isn't very relevant, as languages can and do evolve. Similarly for the opinions of the main developers.
  - ancarda 10y ago
    >Your argument is about ease of use No! My argument is more meta; that this whole discussion is an unproductive waste of time and I can't tell anymore if people are just trolling or looking to start a flame war by bringing up generics in a Go thread. It's noise and it's making Hacker News a worse place. This has been discussed to death already.