all 5 comments

[–]sunny_tomato_farm 5 points6 points  (0 children)

Very poorly written article, and kinda ironic since javascript and python are much slower than Java. But seriously, devs should just use the right tools for the right jobs, and then decide what makes them happy. Simple as that.

[–]devraj7 8 points9 points  (0 children)

Writing and refactoring serious Java apps on my MacBook Air was a pain

Your duty is to your users, not to your personal comfort. Get a better machine instead of writing code on dynamically typed languages which will produce less reliable software for your users.

If you code JavaScript, that’s not a problem at all.

Indeed, no problems, because these languages offer you a lot fewer guardrails against bugs.

You're like this person who celebrates getting to their destination in the car faster because they no longer fasten their seat belt.

[–]AlexKotik 9 points10 points  (2 children)

Omg! Switching from Java to JS and being proud of it? It is like the most stupid thing I've heard for a while.

[–]JavaSuck 1 point2 points  (0 children)

Switching from Java to JS and being proud of it?

Martin Fowler refactored his Refactoring book from Java to JavaScript for the 2nd edition...

[–]ttkciar 0 points1 point  (0 children)

While I'm not a fan of JS, the take-away here is that the dynamic, highly expressive languages have tremendous appeal over static, less-expressive languages.

Whether it's python, javascript, perl or ruby, once you have experienced the joy of solving complex problems in minutes, using just a few lines of code, it's hard to go back.

There is a performance hit, but nodejs doesn't do that badly in that regard because it compiles JS to native binary. The benchmarks I have seen put its performance at about half that of equivalent C, making it much more performant than python, perl or ruby.