5 ms·
Issues? What issues? Most complaints about Go are really just "it doesn't contain my favorite language feature", "I heard the GC isn't even precise so it must s
by _ak 14y ago
Issues? What issues? Most complaints about Go are really just "it doesn't contain my favorite language feature", "I heard the GC isn't even precise so it must suck", "it's too immature", "I couldn't get this library to work within 10 minutes so Go sucks", etc. pp., but people are simply unable to point to any actual pain points that hinder productive use of Go.
- ithkuil 14y agoI really love go, I try to use it whenever I can. That being said, I still have the feeling that having to rewrite a lot of dummy boilerplate code because of lack of generic collections hinders my productivity. I completely understand that introducing that in the language it's a pandora box, etc etc (not only because of compiler's complexity and compilation speed). But still, I have to find a way around that, being DRY has obvious advantages (although depending too much on obscure magic can be a problem); it's not just a random language feature from my favorite language. I'm trying to see whether https://github.com/droundy/gotgo https://github.com/droundy/gotgo helps
- _ak 14y ago> I still have the feeling that having to rewrite a lot of dummy boilerplate code because of lack of generic collections hinders my productivity. Can you give any concrete code examples including a description what you would have liked differently?
- codexon 14y agoWith your logic, the same argument could be applied to PHP. The problem is that Go simply doesn't solve anything new. If Go contains your favorite language features but not mine, then why should I bother to use or hype it? If you want lightweight concurrency with GC you could have gone with Scala, Erlang, or Haskell.