4 ms·
I can't believe that I read a nice article about working on a massive project in Go over a couple of years - a meaningful experience that we could probably all
by johnfn 10y ago
I can't believe that I read a nice article about working on a massive project in Go over a couple of years - a meaningful experience that we could probably all learn from - and the top comment doesn't build on the content of the post at all, but is rather a thinly veiled accusation of "Go is a terrible language".
- cwyers 10y agoReally? Because your profile says you've been a member for over 2700 days, so you should be used to HN comments by now.
- edgyswingset 10y ago> but is rather a thinly veiled accusation of "Go is a terrible language". That's because it is.
- rpeden 10y agoOver time, I've come to notice that once any online forum reaches a certain critical mass of programmers, nearly any mention of a specific programming language will devolve into a flamewar about that language. I find it frustrating, but I also suspect that it's been that case since approximately forever ago. One day I plan to don a flame retardant suit and wade into Usenet archives to see if programmers were as prone to language flamewars 30+ years ago as they are now. I'm guessing the answer is probably yes. :)
- AdieuToLogic 10y ago... if programmers were as prone to language flamewars 30+ years ago as they are now. I'm guessing the answer is probably yes. :) Your guess is spot on. Not only languages (C vs Pascal, "why doesn't anyone use Ada?"), but probably best remembered for the vi vs emacs crusades. Though about 20+ years ago there were some pretty heated exchanges regarding OOP which seem to still smolder to this day (see HN history for evidence :-)). There's a reason why Godwin's law[0] came about :-D 0 - https://en.wikipedia.org/wiki/Godwin%27s_law https://en.wikipedia.org/wiki/Godwin%27s_law
- johnfn 10y agoI think it's the whole bikeshedding thing, where people will jump to talking about the most superficial thing they have an opinion about.