3 ms·

Meanwhile Node is killing it on the backend. Sorry, but this author is just the equivalent of an old man yelling at kids to get off his lawn... but worse, it's

Meanwhile Node is killing it on the backend. Sorry, but this author is just the equivalent of an old man yelling at kids to get off his lawn... but worse, it's not even his lawn, never was, and the "kids" are the ones who built his home over the last 15 years. He looks out of date, out of touch, and unwilling to develop skills and knowledge. Not a good look.

reitanqild 11y ago
Downvoted since clearly hyperbole with 15 years timeframe.
- abritinthebay 11y ago
  13 years. It started in ~2003 that JavaScript as a whole was being approached differently. By 2006 a LOT had changed. In 2008 V8 was released and 2009 Node was released. But that is merely the newest epoch of the current wave. JavaScript has been taken seriously by those paying attention for ~13 years. They've been building the web with it while others complain about it. So sorry, I rounded up by 2 years. But hyperbolic? Not really.
  - reitanqild 11y ago
    For server side javascript the earliest vague reference I can think of is Steve Yegge, - "The Next Big Language" from 2007: http://steve-yegge.blogspot.com/2007/02/next-big-language.html http://steve-yegge.blogspot.com/2007/02/next-big-language.ht... You seriously mean something was brewing 4 years before that?
emodendroket 11y ago
Did you read the article? He considers and rejects that argument.
- abritinthebay 11y ago
  He rejects it, but poorly and badly thought through - like most of the rest of his reasoning in the article
- k__ 11y ago
  Did you? "Node has been ... relegated to a web niche. ERP solutions ... aren’t using Node... don’t expect any serious shop to be washing their ... data through JS code...Fortune 500 shops aren’t basing their businesses on JavaScript ... JavaScript is intrinsically a dysfunctional language.... more flaws than any other programming language... JavaScript is wholly unsuitable for serious software... tens of thousands of lines of code ...difficult to ensure a specific level of quality..." He's just ranting around. Even the "sources" are just scattered links to other rants of him...
uptownJimmy 11y ago
Node isn't "killing it" anywhere, as far as I can see. It's a special-case technology being touted as competition for proper server-side languages, but in reality it is poorly-suited for the job. There's no valid reason why most people should choose JS on the server instead of Ruby, Python, PHP, C# or Java, except that so many people know JS and so many people love shiny "cool" stuff. Node is a deeply flawed and very messy ecosystem. Verdict: no, but thanks.
- abritinthebay 11y ago
  > There's no valid reason why most people should choose JS on the server instead of Ruby, Python, PHP, C# or Java It's faster than the first 3 of those and easier to write than the last 2. It handles concurrency better than the first 3 as well. I'll be sure to let Ebay, Paypal, Yahoo, Walmart, AirBnB, Netflix, Uber.. etc that they are clearly wrong: because you said so.
  - uptownJimmy 11y ago
    I listed some reasonable questions just above this post, and I still don't have a good answer from anyone: what's the current list of apps these companies are running on Node, how special-case are they, how happy are these companies with their Node apps, how big a portion of their code bases are Node, etc? I've seen some links to a few articles that date back 3-5 years, but nothing more current, and nothing very detailed at all. That list of companies you typed out is the same list of companies everybody always types out. I'm wondering about some actual details. I don't think that's unfair.
    - abritinthebay 11y ago
      I'm not an employee of any of those companies (though the one I DO work for is moving to Elixir and Node away from Ruby) so I don't feel I should comment on that. However they all are very active in the conference circuit (and on their engineering blogs) talking about their current work in Node. Its not unfair to ask but not everyone can give you the kind of information you seek.

reitanqild 11y ago

Downvoted since clearly hyperbole with 15 years timeframe.

abritinthebay 11y ago
13 years. It started in ~2003 that JavaScript as a whole was being approached differently. By 2006 a LOT had changed. In 2008 V8 was released and 2009 Node was released. But that is merely the newest epoch of the current wave. JavaScript has been taken seriously by those paying attention for ~13 years. They've been building the web with it while others complain about it. So sorry, I rounded up by 2 years. But hyperbolic? Not really.
- reitanqild 11y ago
  For server side javascript the earliest vague reference I can think of is Steve Yegge, - "The Next Big Language" from 2007: http://steve-yegge.blogspot.com/2007/02/next-big-language.html http://steve-yegge.blogspot.com/2007/02/next-big-language.ht... You seriously mean something was brewing 4 years before that?

emodendroket 11y ago

Did you read the article? He considers and rejects that argument.

abritinthebay 11y ago
He rejects it, but poorly and badly thought through - like most of the rest of his reasoning in the article
k__ 11y ago
Did you? "Node has been ... relegated to a web niche. ERP solutions ... aren’t using Node... don’t expect any serious shop to be washing their ... data through JS code...Fortune 500 shops aren’t basing their businesses on JavaScript ... JavaScript is intrinsically a dysfunctional language.... more flaws than any other programming language... JavaScript is wholly unsuitable for serious software... tens of thousands of lines of code ...difficult to ensure a specific level of quality..." He's just ranting around. Even the "sources" are just scattered links to other rants of him...

uptownJimmy 11y ago

Node isn't "killing it" anywhere, as far as I can see. It's a special-case technology being touted as competition for proper server-side languages, but in reality it is poorly-suited for the job. There's no valid reason why most people should choose JS on the server instead of Ruby, Python, PHP, C# or Java, except that so many people know JS and so many people love shiny "cool" stuff. Node is a deeply flawed and very messy ecosystem. Verdict: no, but thanks.

abritinthebay 11y ago
> There's no valid reason why most people should choose JS on the server instead of Ruby, Python, PHP, C# or Java It's faster than the first 3 of those and easier to write than the last 2. It handles concurrency better than the first 3 as well. I'll be sure to let Ebay, Paypal, Yahoo, Walmart, AirBnB, Netflix, Uber.. etc that they are clearly wrong: because you said so.
- uptownJimmy 11y ago
  I listed some reasonable questions just above this post, and I still don't have a good answer from anyone: what's the current list of apps these companies are running on Node, how special-case are they, how happy are these companies with their Node apps, how big a portion of their code bases are Node, etc? I've seen some links to a few articles that date back 3-5 years, but nothing more current, and nothing very detailed at all. That list of companies you typed out is the same list of companies everybody always types out. I'm wondering about some actual details. I don't think that's unfair.
  - abritinthebay 11y ago
    I'm not an employee of any of those companies (though the one I DO work for is moving to Elixir and Node away from Ruby) so I don't feel I should comment on that. However they all are very active in the conference circuit (and on their engineering blogs) talking about their current work in Node. Its not unfair to ask but not everyone can give you the kind of information you seek.