4 ms·
> A few frameworks are strong contenders to be the successor to rails. Node.js is in the lead. Node.js isn't a framework. What about comparing apples with appl
by danmaz74 11y ago
> A few frameworks are strong contenders to be the successor to rails. Node.js is in the lead.
Node.js isn't a framework. What about comparing apples with apples?
Anyway, I think that the main change that's going on right now is that lots of web apps have a higher and higher percentage of the code written for the front end (web and mobile) rather than the back end.
Rails still has much higher productivity and tooling for back-end development than the Node.js frameworks I've seen for now, but that could become irrelevant for many startups in the medium term, just because a lot of the added value for them will come from the front end rather than the back end.
- Killswitch 11y ago> Node.js isn't a framework. What about comparing apples with apples? What would you call it? Because it's not a language either. JavaScript is the language.
- danmaz74 11y agoEvidently, "framework" suffers from semantic overload here. The article itself says that "Node.js suffers from fragmentation with a half dozen frameworks competing".
- Killswitch 11y agoSo how would we describe Node.js in this sense? It's not a framework, and it's not a language.
- spdionis 11y agoPlatform?
- Killswitch 11y agoI'm going to start calling it a doohicky.
- mattdeboard 11y agoIt's a runtime for JavaScript. It's definitely not a framework.
- Killswitch 11y agoV8 is the runtime.
- mattdeboard 11y agoEr, I'm far, far from a JS expert let alone V8, but I thought V8 does the compilation to machine code and Node serves as the process containing the thread the program is running on, making Node the runtime, and V8 the engine. That and nodejs.org calls it a runtime built on V8 :P