Sven Slootweg @joepie91@pixie.town

It occurs to me that this is rarely said out loud, but it probably should be:

The ability to fork open-source software is important, *but* the idea of "if you disagree then you can just fork it" is basically a lie. It has never worked that way and it will never work that way.

In reality you're dealing with project governance and so there are a lot of social factors (community support, motivation to 'compete' with the established name, etc.) that are critical to not having a fork wither on the vine.

And it's very difficult to pull that off, and usually requires a long history of growing resentment about the leadership of the forked project. This means a fork is rarely the best solution.

@raito No conditions whatsoever, including and up to supporting `null` values, as there is no serialization step involved anywhere (unless you add a serialization stream, of course).

You represent the processing steps as a linear(-ish) Promistream pipeline in your code, but behind the scenes that essentially gets converted into a long chain of Promise handlers, so anything that can go in a Promise (which is everything) can go into a Promistream too :)

@raito So Promistreams are agnostic to the values that go through them; you totally could use them to design some sort of streaming component system (by streaming through component-shaped objects), but Promistreams *themselves* do not do anything with components, and it wouldn't be directly in scope.

Someone actually compared Promistreams to Rx.js earlier today, in concept, so you're probably not far off with your idea :)

(There *is* a plan to write an Rx.js adapter stream which can convert between Rx.js and Promistreams bidirectionally, so if such a component system already exists based on Rx.js, then Promistreams could plausibly interoperate with it)

People joke about "expensing hacker events as work trips" but actually I think that's genuinely a reasonable thing to do, even under the 'conventional' understanding of what constitutes a 'work trip' (for training and education).

There's no rule that says a trip must be boring to qualify as "materially useful to your job"! That idea is just some puritan(?) ideological nonsense, it has no bearing on how the world works.

Promistreams are now officially in beta! (Which mostly just means I have added a little infobox at the top of the page )

https://wiki.slightly.tech/books/projects/page/what-are-promistreams

Basically, they're streams for #JavaScript that are actually nice to work with, have first-class Promise support, handle errors correctly, handle concurrency reliably, interoperate with other stream implementations, and just generally make more sense than Node streams.

You can use them for streaming data, but also for things like task queues or distribution patterns. They can work in any JS environment, and are not limited to Node.js. More documentation will become available soon (especially for more complex cases), but the basic stuff is already explained at the link.

Please give them a try and let me know how it went, and whether you ran into any issues!