Goran Peshanski gphfour

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

enc parameter - 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 - This encourages a lot of random events to be "attached" by other authors which doesn't work. Best to have an uniform (typed) interface so that everyone knows what to expect.
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. When you attach listeners determines what will happen.
no error propagation - we need the

How to setup your own CA with OpenSSL

For educational reasons I've decided to create my own CA. Here is what I learned.

First things first

Lets get some context first.

	PLEASE CHECK THIS REPO WITH THE EXAMPLES THAT YOU CAN RUN:
	https://github.com/apieceofbart/async-testing-with-jest-fake-timers-and-promises

	// Let's say you have a function that does some async operation inside setTimeout (think of polling for data)

	function runInterval(callback, interval = 1000) {
	setInterval(async () => {
	const results = await Promise.resolve(42) // this might fetch some data from server
	callback(results)
	}, interval)