3 ms·
A big mistake for a newcomer to any field is to put too much stock into people's opinions, particularly those that are put disrespectfully. It's a common techni
by enneff 12y ago
A big mistake for a newcomer to any field is to put too much stock into people's opinions, particularly those that are put disrespectfully. It's a common technique among the programming crowd to vocally disparage other people to make yourself seem smarter than you are. This article is one of those.
- hardwaresofton 12y agoDefinitely true, but for someone to be this mournful about the state of the industry is usually indicative of at least a LITTLE problem. I'm acutely aware that it's his personal opinion, I am aware of the pitfalls of bashing-culture (I've fallen into it many times when looking at legacy code), and I didn't uninstall linux and switch to illumos. In this case, I think he has a point (though he states it pretty extremely). At the very least, it's refreshing to read an article every once in a while that isn't simply praising the established platforms of today, or pointing out a small shortcoming (usually that the author fixed and decided to make a blogpost about). I'm currently reading his golang post to see why he thinks this way and if he makes any solid points there that sit well with me, but I value the dissent to popular zeitgeist (not so much how disrespectful he was about it).
- enneff 12y agoDon't get me wrong; there is a lot wrong with the computing world. I just don't think this surly rant does much to illuminate the issues. There's a lot wrong with his post on Go. It's not even worth reading.
- hardwaresofton 12y agoYep... You were right, the golang post barely made any good points -- it was more about toolchain implementation rather than the language...
- the_why_of_y 12y agoThis post? What specifically do you think is wrong with it? http://dtrace.org/blogs/wesolows/2014/12/29/golang-is-trash/ http://dtrace.org/blogs/wesolows/2014/12/29/golang-is-trash/ Its basic point is that you should be using the "gccgo" implementation of Go, not the "gc" one which is badly NIH'ed. He refrains from pointing out any of the obvious issues with the Go language itself since that is not his area of expertise, so if you're coming from a language background then you won't find the post interesting.
- enneff 12y agoI come from the background of working on the Go project for five years. He really doesn't see the trade offs we made when choosing to base the core Go implementation on the plan 9 tool chain, and seems oblivious to the work already done to alleviate some of his complaints. A poorly researched article with no actual insight at best. At worst, a thinly veiled personal attack against the Go authors.
- justin66 12y agoRuss Cox posted a detailed but not comprehensive response here: https://news.ycombinator.com/item?id=8817990 https://news.ycombinator.com/item?id=8817990 HN pretty much ignored it. Perhaps because it wasn't angry or ranty.
- frowaway001 12y agoSays the Golang dude. Pot. Kettle. Black.
- enneff 12y agoShow me an example of me disrespectfully disparaging other people's work. I'll wait.