Article like this needs to be sliced-n-diced in different ways:
1) If you don't know technology X and use it due to hype, you deserve to get burned
Let that be a lesson for anybody.
2) There's no silver bullet
Choosing node.js over web-framework just because you want the front-end and the back-end to use the same code-base is to trade one feature for another: Ruby and Rails still have better tools than Node.js while you get JS all over the place (assuming you're good with JS).
3) Complaining about the language is a sign that you have no clue
I used to think that Java is better than some of the hype dynamic languages out there but I was wrong: Java is better for ME because I _KNOW_ Java Better. If I know Ruby more than I know Java then Ruby is better than Java FOR ME.
4) Don't program using another language's idioms
This is documented left and right already. If you use technology X, find best-practices for technology X. Don't just apply best-practices from technology Y.
Or some of the comments here about Dependency Injection (which is quite common in Java but not so in Python/Ruby).
In the past, I had one instructor that noticed that my QBasic code looked like Fortran. He asked me if I knew Fortran beforehand and I told him that I've taken Fortran before this class.
1) If you don't know technology X and use it due to hype, you deserve to get burned
Let that be a lesson for anybody.
2) There's no silver bullet
Choosing node.js over web-framework just because you want the front-end and the back-end to use the same code-base is to trade one feature for another: Ruby and Rails still have better tools than Node.js while you get JS all over the place (assuming you're good with JS).
3) Complaining about the language is a sign that you have no clue
I used to think that Java is better than some of the hype dynamic languages out there but I was wrong: Java is better for ME because I _KNOW_ Java Better. If I know Ruby more than I know Java then Ruby is better than Java FOR ME.
4) Don't program using another language's idioms
This is documented left and right already. If you use technology X, find best-practices for technology X. Don't just apply best-practices from technology Y.
http://dirtsimple.org/2004/12/python-is-not-java.html
Or some of the comments here about Dependency Injection (which is quite common in Java but not so in Python/Ruby).
In the past, I had one instructor that noticed that my QBasic code looked like Fortran. He asked me if I knew Fortran beforehand and I told him that I've taken Fortran before this class.
People see and notice.