back to article Node.js says all is forgiven, welcomes io.js fork back into the fold

The Node.js Foundation has released version 4.0.0 of the Node.js, the first version that reunites the JavaScript-based server-side web application framework with its io.js fork. "This release represents countless hours of hard work encapsulated in both the Node.js project and the io.js project that are now combined in a single …

  1. Anonymous Coward
    Anonymous Coward

    Time for me to learn this thing now and use it, rather than dabble. When a project has been forked and then re-united, you gain a certain level of confidence in its maturity and facility.


    1. Anonymous Coward


      Not me. The fork and divergence spooked me into looking at alternatives. Although experienced in node / javascript, I chose to start the new project in golang, and the sunk cost of learning go are already starting to pay off.

      node's npm ecosystem is quantity over quality. Many packages are poor quality and/or abandoned. javascript's looseness definitely contributes to this. es6 allows and encourages better code, but many packages would need considerable es6 re-factoring. Eg: Class model, callback hell vs Promise chains. Modern javascript data structures such as Map, Set, and typed arrays.

      If you do pick node, look into strong_mode. It's like strict mode, but an even stricter sub-set of javascript, which encourages better code, and prevents many v8 performance foot-guns going forward.

      nodejs: Low boiler-plate. Very rapid prototyping of server applications. Vast package library.

      golang: Steeper learning curve, but eventually zen-like. Concurrency baked into its core. Strong / static typing. High quality packages.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Other stories you might like