As a commenter upthread pointed out, Go and serverside Javascript are aimed at very different use cases and audiences.
As a commenter upthread pointed out, Go and serverside Javascript are aimed at very different use cases and audiences.
You go fanatics are incorrigible.
What he's describing is far more than possible using interfaces. I have plenty of code that does so.
How is that "wrong and he knows it". Your worse than any Go fan here. Where the hell does someone get off being vitriolic about a language or someone's preference for that language. Pathetic, at least have the balls to post under your real account.
That having been said, as an "incorrigible Go fan", I would love to see proper generics. It's something I'm enjoying in Rust. It's also something that everyone is open to adding in Go 2, so it doesn't necessarily have to be a permanent absence from Go.
I assume they're not gainfully employed, or else they would understand that the two languages/platforms have very different goals and principles.
Chord was on about "Rails" is better, couldn't fathom a web world without MVC and failed to understand that Rails was just a framework on Ruby and that one could write similar helpers in Go.
It was the perfect example of Dunning-Kruger. Painful to witness.
Something about golang just seems to attract a certain flavor of nutters.