-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
io.js stream stability #288
Comments
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. |
@rvagg thank you for the insight. |
@rvagg I think you linked to a wrong issue/PR. |
thanks, fixed (I think you @-mentioned the wrong person) |
Is it still unstable?
https://github.com/iojs/io.js/blob/v1.x/doc/api/stream.markdown#stream
The text was updated successfully, but these errors were encountered: