Why not create an npm module that represents what you'd like to see as an interface wrapping node's implementation and propose your new interface?
This way you can try building something with it. You'll first need to implement how you see a synchronous stream in the first place. Streams can be a complex beast though. Do you want a synchronous or asynchronous implementation or both? Will they consume like generators, async iteration (for await of)? What about queueing and back pressure? On Sat, Apr 28, 2018, 22:28 Chet Michals <[email protected]> wrote: > Working between a number of different ECMAScript environments over the > years, such as in Java with Rhino and Nashorn, Node.js, and various web > browsers, one thing I have noticed is that there is no standard > input/output/error stream like most other languages support, and each > ecosystem tends to define their own host objects to deal with these, like > the console object in most Web Browsers (Which is at least defined in a > WHATWG Living Standard), the process object in Node.js, and the print > object in Nashorn. > > I feel for long term portability, the 3 standard IO streams should be > added to the spec in some way, > > Is there a reason I am not seeing as to why this wouldn't be desired? > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
