You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I'm also confident enough to say that yes, it should still be considered unstable. io.js already has a very different streams codebase to Node 0.10 (just like Node 0.11 does). Have a look at https://github.com/iojs/readable-stream/compare/v0.10 to get a taste of this. The current version in io.js and in readable-stream/master is generally referred to as "streams3" while what's in 0.10 is "streams2". I'd call this unstable.
Activity
rvagg commentedon Jan 12, 2015
Agreeing with @sonewman, we should move discussion into nodejs/readable-stream#97 or somewhere else in iojs/readable-stream.
However, I'm also confident enough to say that yes, it should still be considered unstable. io.js already has a very different streams codebase to Node 0.10 (just like Node 0.11 does). Have a look at https://github.com/iojs/readable-stream/compare/v0.10 to get a taste of this. The current version in io.js and in readable-stream/master is generally referred to as "streams3" while what's in 0.10 is "streams2". I'd call this unstable.
jmcbee commentedon Jan 12, 2015
@rvagg thank you for the insight.
jmcbee commentedon Jan 12, 2015
@rvagg I think you linked to a wrong issue/PR.
rvagg commentedon Jan 12, 2015
thanks, fixed (I think you @-mentioned the wrong person)