3 ms·

So for those who wonder: In the TC meeting today we came up with a vision for the first release. First, a few assumptions we've internalized that prob

by DAddYE 12y ago

So for those who wonder: In the TC meeting today we came up with a vision for the first release. First, a few assumptions we've internalized that probably need to be stated for this to make sense. - Node is pretty damn stable already. There are huge companies with it in production, 100K+ modules, etc. It is already far more stable that its pre-1.0 release tag suggests. - Releasing more frequently leads to a more stable product, not a less stable product. - The entire ecosystem uses semver while node uses a confusing even/odd release structure. If people disagree with any of those assumptions then they certainly won't agree with anything the TC determined for the initial release. So, first release of io.js: - January 13th (Fedor's Birthday!) target date. - Will be 1.0-alpha1, with alpha releases continuing until 1.0.0. - Switching to semver. - We will be taking new v8 releases as fast as possible moving forward. - Trying to get to a weekly release cycle. Which version number is incremented each week is determined by the changes and whether or not they are breaking. Again, following semver. Some questions still left open: - Are there any changes other than dep upgrades and fixes required for 1.0? - Is build confident we can have enough automation in place to hit this date. - Is the plan to have the installer install an iojs binary and an alias to node? Source: https://github.com/iojs/io.js/issues/28 https://github.com/iojs/io.js/issues/28

bcanzanella 12y ago
So, they're going to change a few things around the build process and versioning? I wonder if there will be any plans to address core functionality, namely callbacks vs promises.
- jonny_eh 12y ago
  I assume language features remain the domain of the V8 engine, which is pulled in from Google.
  - Touche 12y ago
    The parent was referring to how, in the Node world, typically errors are the first argument of a callback function(err, value). Promises will be added to Node soon, but the question was whether they will change all of their APIs to use those instead of the current callback method.
    - bcanzanella 12y ago
      precisely
- kybernetikos 12y ago
  Yeah. I'd love to see a node/npm fork that used es6 modules instead/as well as npm modules, and promises instead of callbacks throughout the api. Everything else the same, but something that will use the newer stuff that is becoming available a bit sooner than the node ecosystem will.

by DAddYE 12y ago

bcanzanella 12y ago

So, they're going to change a few things around the build process and versioning? I wonder if there will be any plans to address core functionality, namely callbacks vs promises.

jonny_eh 12y ago
I assume language features remain the domain of the V8 engine, which is pulled in from Google.
- Touche 12y ago
  The parent was referring to how, in the Node world, typically errors are the first argument of a callback function(err, value). Promises will be added to Node soon, but the question was whether they will change all of their APIs to use those instead of the current callback method.
  - bcanzanella 12y ago
    precisely
kybernetikos 12y ago
Yeah. I'd love to see a node/npm fork that used es6 modules instead/as well as npm modules, and promises instead of callbacks throughout the api. Everything else the same, but something that will use the newer stuff that is becoming available a bit sooner than the node ecosystem will.