Join Quora for free to read this answer.
Not likely.
Name:
Anonymous2012-11-15 23:18
Jacob Kaplan-Moss, Lead developer of Django.
111 votes by Kornelis Sietsma, Jason Roy, Biju Chacko, (more)
I see three major "wins" that Node.js has over most other development environments (including Python):
It's built to handle asynchronous I/O from the ground up. Other environments have async. I/O features, but Node's the first environment where it's really pervasive. In most environments you'll find only limited pieces available in async. flavors, but in Node everything (or nearly everything) is async.-only. It's actually hard to write non-async. code in Node!
Now, there's some debate over whether async. programming is really the silver bullet some claim it is, but in my mind there's little doubt that it's a really good match to a lot of common web- and network-development problems.
It's "just JavaScript." Every time I context switch between Python on the backend and JavaScript on the frontend I waste stupid amounts of time making silly syntax errors — semicolons in my Python, missing braces in my JavaScript, etc. Some days I might switch a dozen or more times, and it really feels like I'm wasting brain cycles swapping in and out my language knowledge. Staying in a single language feels faster.
It's new, so it has the benefit of being able to learn from previous languages' and environments' mistakes. Better, Node can correct those mistakes without the backwards-compatibility concerns. For example, the Node package installer, npm, is already quite a bit better than many of its equivalents. All in all, Node feels very polished and modern; it hasn't had time to accumulate the cruft other languages/environments have.
(Sadly, I'm all too sure it will accumulate this cruft eventually. Everything new feels old eventually.)
I highly recommend that you take the time to learn Node — it'll make you a better developer, whatever you end up using. I learned Node last year, and I'm very happy I did. It's a cool piece of software, and it's a great tool to have in your toolbox.
It's "just JavaScript." Every time I context switch between Python on the backend and JavaScript on the frontend I waste stupid amounts of time making silly syntax errors — semicolons in my Python, missing braces in my JavaScript, etc. Some days I might switch a dozen or more times, and it really feels like I'm wasting brain cycles swapping in and out my language knowledge. Staying in a single language feels faster.
A+++ WebDev -- would hire again!
>>7
I wouldn't. I switch between Python and JS multiple times per day and I have no problems like those he described. And I myself am rather dumb and talentless. I can imagine how dumb this fucking retard must be.
However I'd have to add that I'm actually an advocate of only using one or maybe two languages when building something and not like 5 different langs, like WebDevs have to (HTML + CSS + Clientside (JS) + Serverside + Database + ??? + Flash?).
But then again, a web-bytecode that could be compiled to from any language just isn't possible, as we all know.