Hacker News new | ask | show | jobs
by lobster_johnson 3821 days ago
It's also worth mentioning that the Node community took a long time to get streams right, and "Streams 2.0" is still poorly documented.

For example, a major feature of the redesign is backpressure support, but it's not at all obvious how it's supposed to work, and there are no mechanisms available in the standard library to tweak it.

Streams also still have odd issues you would not expect in a mature release. (Error propagation, for example, is quite broken in practice; if you string together a series of pipe() operations, emitted errors won't propagate up the chain properly.)

I haven't looked very closely at Elixir's streams, but the fact that they are based on lazy function evaluation makes them inherently better than what Node.js offers.