3 ms·
Odd state? It certainly is... but it is only what... a year or two old now? It seems to me that what is missing is a clear winner. Sure, competition from a num
by latchkey 14y ago
Odd state? It certainly is... but it is only what... a year or two old now?
It seems to me that what is missing is a clear winner. Sure, competition from a number of different fronts is really great, but I think what made Java tick for a long time was JBoss and Spring. For Ruby, it is Rails. I'm sure Python has Django and others.
Clearly lots of people are working on it, but a powerhouse framework for NodeJS just hasn't surfaced quite yet. The OP's mention of security being bolted on as an afterthought really is something that makes me shudder. I can't imagine building a large scale public facing system without method level access control. I fear a whole new generation of injection type attacks against NodeJS frameworks.
While it is fun to play with all the shiny new NodeJS toys, I don't see why sticking with tried and true on the backend (take your pick of Python / Ruby / Java) is such a big deal. A lot of the cool features that are being touted in the NodeJS frameworks have been already done elsewhere for much longer.
For me, I've really successfully used NodeJS in one area where it really shines... scraping web pages... but that is simply because working with a jquery-like interface to the DOM, on the server side, is amazing.
In the end, it seems like if you're bootstrapping a company / product (like many of us here are) and trying to pick what to use for your base platform, the obvious choice is building features instead of building frameworks. This means you stick with the tried and true and hope that in the future, the shiny new toys mature a bit more before you go down that path.
- gcr 14y agoPardon? NodeJS is almost four years old now.
- latchkey 14y agoI wasn't referring to node directly. I'm talking about the frameworks that have sprung up around it.
- mcantelon 14y ago>It seems to me that what is missing is a clear winner. Although there are a lot of great frameworks, Express is the 13th most watched repo on GitHub and seems to be what most Node folks use.
- wehriam 14y agoAfter years of working with Django, I choose Node because of an abundance of developers with experience in Javascript, an environment free of context shifts when moving between languages, and code portable to the front and back end of the stack. Python is much "shinier" to me, but I think Node will make my company more competitive.
- dcosson 14y ago> A lot of the cool features that are being touted in the NodeJS frameworks have been already done elsewhere for much longer. Are you including Derby.js and Meteor.js in this? The main example the article uses is the way these frameworks seamlessly sync to your datastore and other clients, and the server is running the same code so you don't have to write almost any boilerplate to do this. This seems like a unique property of running javascript on server and browser, and I don't know of anything in Python/Ruby/Java that even tries to do this. It seems like it would inevitably be more complicated and require duplication of code. Unless you had a framework that compiled your model and view code from one of these languages to or from javascript (which I've always thought would be cool but now seems like a worse solution than Meteor or Derby)