Stories
Slash Boxes
Comments

SoylentNews is people

Interview with Mikeal Rogers: Node.js Fork that Ended up as a Giant, Unifying Step Forward

posted by martyb on Sunday June 21 2015, @08:17AM   Printer-friendly
from the two-nodes-back-into-one dept.

tonymercmobily writes with a FreeSoftwareMagazine interview:

Node.js is the software that allows you to run Javascript to create powerful server-side applications by using Google's V8 Javascript Engine. As a Node developer myself, I have always felt frustrated by seeing that Joyent, the company behind Node.s, was extremely conservative in terms of upgrading node to use the latest V8 version; the project was also struggling to get developers to actually contribute to code. This is why Fedor Indutny did the unthinkable: forked node and created IO.js. Today, the two projects are uniting possibly offering developers the best of both worlds

Original Submission

 
This discussion has been archived. No new comments can be posted.
Interview with Mikeal Rogers: Node.js Fork that Ended up as a Giant, Unifying Step Forward | Log In/Create an Account | Top | 39 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 0) by Anonymous Coward on Sunday June 21 2015, @11:22AM

    by Anonymous Coward on Sunday June 21 2015, @11:22AM (#199026)

    Actually, I'm a nodeJs developer myself. That's rather the point of it, it is not slow and can act very much like a full desktop application inside a web browser.

    There is overhead for a scripted language, but you should probably understand that a computer in 2001 was powerful enough to run this script. It is now 2015 and even cell phones now have the horsepower to run these scripts so your argument about slowness has never actually panned out in operation.

  • (Score: 3, Informative) by JNCF on Sunday June 21 2015, @04:19PM

    by JNCF (4317) on Sunday June 21 2015, @04:19PM (#199109) Journal

    Node is not inside the web browser. You can compile CommonJS (which node uses) into normal ECMAScript that can run in a browser, but the web browser definitely isn't running node. Processing power (and interpreter efficiency) has improved, but there is still a huge gap between ECMAScript in a browser and compiled C. Projects like asm.js and WebAssembly are trying to bridge that gap, but they haven't yet. The fact that they exist shows that there is a need for faster code execution than modern ECMAScript allows. We might as well be honest and up-front about this weakness. There are other reasons to use ECMAScript, and node.