Node streams - a fractal of weird design
and a potential refactor that could fix that
This is a list of issues and confusions I've encountered with node streams, and things I wish were designed and implemented differently. If promise-streams is ever going to change to a design that doesn't build on top of node streams, this would be a list of mistakes to avoid
encparameter - Why is encoding always passed together with the data? It should be a separate concern. It doesn't even make sense in objectMode
- eventemitter base - There is no reason to use an uncomposable grab-bag of stringy events as a base
- relying on nextTick etc for execution order - This is very unreliable and causes all sorts of unpredictable rules for implementers which are not documented anywhere.
- no error propagation