So far I don't see any benefit in node.js over mature enterprise frameworks.
That's funny, cause I'd prefer literally anything that isn't called an enterprise framework.
Node.js - Convincing the boss guide
11–20 of 85 posts
Re: Node.js - Convincing the boss guide
#12Here's something oft-understated:
As a web developer, you sit on the intersection of engineering, design and art. You're lucky enough to live at a time where there are numerous production-ready tools with which to do your job. If you choose a tool that you're excited to explore, with an active and fast-moving ecosystem, your excitement and enthusiasm will make you happier and more likely to do a better job.
Someone down the thread said this:
> So far I don't see any benefit in node.js over mature enterprise frameworks.
If I was only allowed to work in ASP.NET, I'd be looking to change careers pretty fast.
Don't underestimate the value of enthusiasm - especially if you're a boss.
Re: Node.js - Convincing the boss guide
#13The usecase of building JSON api servers are often used. Can someone give some examples of node JSON api implementations?
Do you mean companies using it? Look for SimpleGeo. Do you mean librairies? Look for Express or Restify.
Re: Node.js - Convincing the boss guide
#14Here's something oft-understated: As a web developer, you sit on the intersection of engineering, design and art. You're lucky enough to live at a time where there are numerous production-ready tools with which to do your job. If you choose a tool that you're excited to explore, with an active and fast-moving ecosystem, your excitement and enthusiasm will make you happier and more likely to do a better job. Someone d…
> Don't underestimate the value of enthusiasm - especially if you're a boss.
Indeed, and your advice is wisely directed at bosses. However, it's a bit harder (though not impossible) for a developer to use this argument successfully: "Let me use Node because I'll be more excited about the project."
Re: Node.js - Convincing the boss guide
#15So far I don't see any benefit in node.js over mature enterprise frameworks.
The whole point of node.js and it's ecosystem is to avoid anything that looks like an 'enterprise framework', rather it's a collection of lots of little modules that each do one thing and one thing well and that can build on top of each other (turtles all the way down).
Re: Node.js - Convincing the boss guide
#16I love that this started with bad use cases.
Re: Node.js - Convincing the boss guide
#17Here's something oft-understated: As a web developer, you sit on the intersection of engineering, design and art. You're lucky enough to live at a time where there are numerous production-ready tools with which to do your job. If you choose a tool that you're excited to explore, with an active and fast-moving ecosystem, your excitement and enthusiasm will make you happier and more likely to do a better job. Someone d…
> Don't underestimate the value of enthusiasm - especially if you're a boss. Indeed, and your advice is wisely directed at bosses. However, it's a bit harder (though not impossible) for a developer to use this argument successfully: "Let me use Node because I'll be more excited about the project."
That does sound true, although in some cases, "It will help with recruitment" might help.
Re: Node.js - Convincing the boss guide
#18Why is non-blocking IO radical? Tons of libraries and frameworks offered it much before node, including twisted, Java's NIO, and the entire System.Net namespace in .NET. Other than that, surprisingly sensible advice.
It's not radical, it's just occasionally more confusing than blocking io to implement, and doesn't really have any performance benefits in the multicore world.
I'm actually using node for a side project right now as part of re-learning web development (been back-end the last few years), and using javascript as a client language, server language, and db query language via mongo is a neat environment. Also, npm rocks. But don't listen to anyone who tells you they use node+mongo to handle their WEB SCALE PERFORMANCE. If they really had that problem, they'd be better off using the java ecosystem or, if they really wanted to go hardcore, using a lot of C. But Java's unfashionable and C's ridiculous to write a web app.
Re: Node.js - Convincing the boss guide
#19JavaScript seems to be having the same problem that other languages have developed over usage time. It becomes increasingly difficult to know what package does what and more importantly information of the pros and cons of the package. Does anyone know of a link to something similar to what I'm talking about? Say something meaningful about the top N (where N might be 10 or so) packages---what they do, the good and the…
Check out the Node Toolbox: http://toolbox.no.de/
It doesn't seem as fleshed out as the Ruby Toolbox (https://www.ruby-toolbox.com) and could use a bit more editorial for your purposes, but it's a good place to start.
Re: Node.js - Convincing the boss guide
#20> Bad Use Cases: CPU heavy apps
I wouldn't say that Node (i.e. V8) is a bad use case for CPU-heavy apps. In math/statistics for example, V8 stacks up well against other scripting alternatives. See e.g. the benchmarks here:
Of course it's still not as fast as C++, but not terribly off either. Expect dramatic improvements here thanks to the push for making web apps faster.