Streams are more consistent, faster, and 100% backwards compatible as
of 0.10. The "compatibility mode" aka "old mode" is folded into the
API more cleanly. You can `pause()` a flowing stream, and then start
calling `read()` again safely. We'll keep exposing streams from core
APIs, and advocating extending the stream base classes in userland
programs.
Forking is not an option
There are not so much insane people
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Not true. When someone (or even a few) say it sucks and no one agrees then he is usually wrong.
--
> Sure. Always follow the majority rule!
I wasn't saying anything about what action to take. I was just stating a statistical fact.
Thank you Isaac, and all node contributors.
I am glad the focus is now on refinement and longevity in a non-breaking way. You mention performance improvement and I am curious how much there is left to squeeze out and where do you think the gains are to be made?
Any mention about changes in HTTP core module? A couple of months ago you (Isaac) had a talk where you said that there are some rooms (and plans) for rewriting HTTP core-module as well as current Buffer implementation.
--
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> > nodes, which would together make up your app?>> Lots of people are doing this now. (Walmart, stackvm, Joyent, and the> npm website all come to mind.)And how's the experience been so far?In comparison to developing and running a single-process app, this quite super difficult and the experience is bad.
then you can deprecate almost half the functions at: http://nodejs.org/api/fs.html (clue: the Sync versions)
pure node.js:
var fs = require("fs");
fs.readFile('/etc/passwd', function (err, data) {
if (err) throw err;
console.log(data);
});
using wait.for:
var fs = require("fs"), wait=require('wait.for');
// in a fiber...
console.log(wait.for(fd.readfile,'/etc/passwd'));
See my topic, about the yielded style programming... and say goodbye to the callback hell. ;)