What are the consequences of node.js?

Question

Hey guys, I read about node.js recently. I saw a lot of articles about how cool it is, and all from some famous people. Given the inertia this project has, and that I am currently studying javascript and jQuery, the project caught my attention. I understand that many people are delighted with this, but I do not quite understand what the consequences are .

I understand that he is event driven and not blocked, and all this, but I am confused about his intentions.

Does node.js mean that we have a foundation for running server-side Javascript, so that later, maybe someone will create Ruby on Rails or the ASP.NET MVC equivalent for node.js / Javascript? Perhaps there are already web frameworks there, but if so, I have not heard the hype machine.

Hope my question is clear.

Answer 1

I think you can hope that this will be more like twisted for Python, not. rails for Ruby is a rich, powerful environment, but still one requires skill and care for proper use, because asynchronous programming is always like that ... it's the price you pay for its absolutely amazing performance potential.

There were Javascript server frameworks, but with server-side Javascript has never been a really popular option, such structures have never received a "critical mass" of support and enthusiasm, such as jQuery , or rails for server-side rubies.

I doubt that asynchronous programming (with its subtlety and difficulty) will be the defining trigger for the "mass movement" (hey, I hope I'm wrong, but I see, for example, the relative popularity of Python Django, amazing performance compared to Twisted, with _all_ amazing performance ... but also the internal complexity! -).

OTOH other developments (such as the mere presence of powerful, high-performance and reliable Javascript engines such as V8) are likely to ultimately lead to wide access (non-async ;-) on the Javascript server side, and, as a result, the possibility Development (or porting, for example, of a structure such as dojo, can already offer a lot for a server-side JS application, only parts of it are actually client-side) powerful, simple, and therefore ultimately a popular structure. However, I would not hold my breath, expecting this ...

Answer 2

I think that the main consequences are double: tremendous performance and scalability, as well as the ability to create web applications in which two or more people can work in the same web application at the same time, watching what others are doing, present. This latter is not only of great importance for web games, but also for collaboration tools, etc.

It appears that node.js is exactly what the web needs in real time. To do this, you also need to check out Socket.IO , which provides cross-browser HTML5 web sockets. Combined with node.js, this creates an incredible platform.

See what knockout did in node.js for some examples of what can be done.

Answer 3

Node.js is an application server that is not yet another webapp server. As the article says, this eliminates the need to write an event loop and use two languages ​​for writing applications (python / java / ruby ​​/ php backend, js frontend). Since it is based on Google's V8 Engine, it is very fast and has a small amount of memory.

There's a web service structure called GeddyJS, and Node.js comes with a set of libraries for I / O, database, and math. You can also expand it with add-ons, although the last time I checked the documentation was still a bit rude.

Answer 4

There is a node framework called bogart, which you can easily use the MVC template and mustache or common-ejs for templates.

http://github.com/nrstott/bogart