Suggestion: Add Standard IO Streams

Isiah Meadows isiahmeadows at
Sun Apr 29 07:11:59 UTC 2018

One good area where you don't want heavy streams is in memory-constrained
devices. Also, streams are inherently very OS-dependent, but
hardware-independent, and they aren't very broadly useful.

I'd like this to be solved cohesively out of spec first, given the half
dozen or so existing formalisms.

(Not a TC39 member, so take this with a grain of salt.)

On Sun, Apr 29, 2018, 01:28 Chet Michals <chetmichals at> 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
> es-discuss at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list