> You've got to filter the noise out. Don't submit every article about something to HN. Don't tell your friends "hey, read this article about a guy memoizing fib, completely missing the point that it was an example CPU-bound algorithm". This is all noise, people that don't know what they're talking about talking.
>... Programming is hard. Let's stop blogging.
The problem with this sentiment is right now too many programmers equate popularity with quality. Their only esthetic is "X number of people follow the project on github". Combine this with the relative inexperience of most programmers and we've got a situation where you can easily flood the market with shitty technologies that only work because everyone believes in them, not because they actually work.
I'm not really talking about Node here, but more your assertion that "this is all noise and us serious real programmers should ignore it". The sad reality is, real serious programmers should speak out about shitty popular technologies before every job requires "20 years Node.js experience".
I'd love for the state of the art to be defined by the state of the art, but sadly, it's currently defined by the best marketing and propaganda. Answering that propaganda with criticism and writing better software is the real answer.
Didn't a similar event occurred a few years back (in HN as well)? Like around 2006-2007 with Ruby on Rails and the framework war? Big waves, big disagreements, flame-wars.
Good prediction though Zed, I'm seeing ghetto Ruby (Rails related code) lately.
Then it becomes the language wars between newer dynamic/functional languages.
Now it becomes Node.js vs the rest of the world. Are we going to see crappy JavaScript code soon?
PS: At the very least, Rails brings real productivity value to the table (cause all other frameworks sucks back then).
>... Programming is hard. Let's stop blogging.
The problem with this sentiment is right now too many programmers equate popularity with quality. Their only esthetic is "X number of people follow the project on github". Combine this with the relative inexperience of most programmers and we've got a situation where you can easily flood the market with shitty technologies that only work because everyone believes in them, not because they actually work.
I'm not really talking about Node here, but more your assertion that "this is all noise and us serious real programmers should ignore it". The sad reality is, real serious programmers should speak out about shitty popular technologies before every job requires "20 years Node.js experience".
I'd love for the state of the art to be defined by the state of the art, but sadly, it's currently defined by the best marketing and propaganda. Answering that propaganda with criticism and writing better software is the real answer.