Re:Why Go Is Not Good (2014)
by thegeekpirate on Wednesday December 09, 2015 @01:29PM
(#10705671)
No one says you don't need generics. Here's rsc explaining why it's not in the language: https://news.ycombinator.com/item?id=9622417
No piece of feedback is ignored, I'm not sure how you've gotten that idea.
It's funny that you set Java aside based on something that it does which you do not need. I am not convinced that Go solves any problem that Java can't solve, other then it doesn't have a baggage of 20 years worth of bad open source libraries and a culture of writing 20 layers of abstraction where no layers are needed.
Re:Why Go Is Not Good (2014)
by slantedview on Wednesday December 09, 2015 @01:21PM
(#10705594)
"it doesn't have a baggage of 20 years worth of bad open source libraries"
Give Go some time. It's inflexibility will inevitably yield some interesting baggage of its own.
Re:Why Go Is Not Good (2014)
by commentzorro on Wednesday December 09, 2015 @06:39PM
(#10707730)
SO CLOSE! You almost got there. I DO want a language that replaces C, Java, Python, etc. It must have: garbage collection, compiles, and compiles to single static executable with no run time dependencies outside a clean install of the OS, and it must have no requirement for me to think about memory layout/management.
BUT, it must also have a nice set of high level abstractions. For web and application level stuff rather than system level stuff.
So, what's that magic language? Really!
Go is almost that language, but it "missed it by that much."
For those who are still arguing about what Go replaces (C? Java? Python?), I try to look at it practically. In the interest of productivity, I might want a language with garbage collection. Ok, so let's set C aside. In the interest of performance, I might want a compiled language. Ok, so let's set Python aside. And maybe I don't care a great deal about portability, so set JVM languages aside.
Go feels like a very practical language, and that's because it is a practical choice for a lot of people.
I hope the Go community does a better job of embracing feedback and caring about language design. It's young enough that breaking improvements could help in the long-term, even if they hurt in the short-term.