"the main backend node.js consulting company in Europe" asserts that Node.js is becoming the go-to technology in Enterprise.
Provides a couple of big name companies and essentially zero evidence.
This is fluff at best.
Why Node.js is becoming the go-to technology in the Enterprise
31–40 of 75 posts
Re: Why Node.js is becoming the go-to technology in the Enterprise
#32Somebody should start a "Vogue for Developers", so we can just stop pretending. Most of this article and most of this thread is about fashion, not technology.
But that applies to a lot of topics on HN.
Re: Why Node.js is becoming the go-to technology in the Enterprise
#33It's a little tiring to see some of the same old fallacies about Node repeated ad infinitum in this thread. I suspect a lot of the complaints stem from poor development practices or not understanding norms in JS. JS isn't without its flaws, but can we at least put a few fallacies to rest: > callback hell There's no reason to be in callback hell if you use an asynchronous control flow library and stick to the standard…
>> Strict typing won't make you a better developer
It won't make you a worse developer either. Loose typing can make you a worse developer because it's easier to make mistakes that sometimes aren't caught until after it's in production.
Re: Why Node.js is becoming the go-to technology in the Enterprise
#34It's a little tiring to see some of the same old fallacies about Node repeated ad infinitum in this thread. I suspect a lot of the complaints stem from poor development practices or not understanding norms in JS. JS isn't without its flaws, but can we at least put a few fallacies to rest: > callback hell There's no reason to be in callback hell if you use an asynchronous control flow library and stick to the standard…
"There's no reason to be in callback hell if you use an asynchronous control flow library"
There's no good reason to pile flawed layers on top of eachother. If you have a fully yieldable/resumable VM (e.g. Lua), you can just solve the problem properly in the first place, in a way that doesn't then require a second or third layer of workarounds to be usable.
Re: Why Node.js is becoming the go-to technology in the Enterprise
#35And then as soon as Derpys Mansion new language comes out all the newcomers will flock to that and you're entire staff will leave to go work for some startup. The reason why "Enterprise" uses the software they do is not because it's the fastest, or most suitable for the job. It's that it's been in production for many years and has a large ecosystem and strong commercial backing. Along with a strong workforce that isn…
Amen. I'd add that while JS is great for form validation, trying to make it into a first class language is a bit laughable. For example, if you want to define a function in a namespace, it's up to you which half dozen "patterns" you use to emulate namespaces in the language that lacks them. Same goes for private method/variables, continuations, classes... or more features of other common language. Add to that the type coercion cluster and the ability for attackers to redefine core language types (make 1 evaluate to false) and JS is still a bit of a anything goes wild west of a language (first class functions are fun).
FWIW, I've written a few 100KLoC of production JS code, but man, I'd really rather use Java/C#/PHP as everyone in JS land has to bend over backwards to try to have the features that are standard out of the box in other languages.
Re: Why Node.js is becoming the go-to technology in the Enterprise
#36And then as soon as Derpys Mansion new language comes out all the newcomers will flock to that and you're entire staff will leave to go work for some startup. The reason why "Enterprise" uses the software they do is not because it's the fastest, or most suitable for the job. It's that it's been in production for many years and has a large ecosystem and strong commercial backing. Along with a strong workforce that isn…
Amen. I'd add that while JS is great for form validation, trying to make it into a first class language is a bit laughable. For example, if you want to define a function in a namespace, it's up to you which half dozen "patterns" you use to emulate namespaces in the language that lacks them. Same goes for private method/variables, continuations, classes... or more features of other common language. Add to that the typ…
[deleted]
Re: Why Node.js is becoming the go-to technology in the Enterprise
#37It's a little tiring to see some of the same old fallacies about Node repeated ad infinitum in this thread. I suspect a lot of the complaints stem from poor development practices or not understanding norms in JS. JS isn't without its flaws, but can we at least put a few fallacies to rest: > callback hell There's no reason to be in callback hell if you use an asynchronous control flow library and stick to the standard…
But... if you're going to bolt on an "async" library, bolt on threading, and bolt on strict typing, why not use something that starts with that stuff? And ends up doing it better since it was actually created with that stuff in mind, instead of aftermarket bolt-ons?
Saying that those things "fix" Node amounts to an admission that you shouldn't have started with Node in the first place.
Re: Why Node.js is becoming the go-to technology in the Enterprise
#38I frequently write modules that I use on both the client and server side of a web application because I'm writing in the same language on both the client and server.
This sort of convergence is why node is so popular.
Pretending like this is some sort of fashionable trend like bell-bottoms is just plain silly.
Re: Why Node.js is becoming the go-to technology in the Enterprise
#39The real reason is quite simple. And I'm not trying to be bitter or anything, rather think like a businessman. The reason is... it's full of JavaScript kids out there, and because they're so many, they're all replaceable, and cheap. Like the commodity hardware servers they're programming. It's neat to cast this as "easy to attract and retain talent", but "rapid innovation" and "developer happiness" (especially consid…
[deleted]
Re: Why Node.js is becoming the go-to technology in the Enterprise
#40These stories about switching to node are pretty funny: "I switched from a dump truck to a motorbike and now I can drive way faster!" Node.js isn't really faster than most other popular languages with an evented library, but if switching to Node involves scrapping years of enterprise cruft, then maybe it's worth it. By the way, enterprise adoption of Node is surely a sign that we need to jump ship. Glad I got out of…
What did you switch to after abandoning Rails? I consider the tooling and rails ecosystem to be the best for small, agile projects and I'm really interested in the alternatives.
I switched to node.js because it was the trendy new thing and I could charge 3x the rate of boring mainstream programmers to deliver the same product, except worse (because it's node.js).
I need a new thing though, since apparently node.js is getting too mainstream. Maybe if I can convince enough businesses that they NEED clojure, then I can go that route.