My first advice to junior contributors is to STOP using vibe coding for PRs. OSS is always about people more than about code. We don't need more code generated by LLM, we need more people who care.

Need the TypeScript team to improve variadic tuples...

Challenge Accepted: WebStreams + WebSockets, No Libs
s.tritarget.org/q

I moved your code to Stackblitz, so it feels a bit more organised across files: stackblitz.com/edit/simples...

Feel free to clone it under your account, in case

So at this point, the real difference isn’t just about libraries, but about paradigms. Your approach is still mostly imperative, while what we’re pioneering is the Stream-Oriented paradigm, aiming to elevate the overall architecture and clarity of applications, not just the tools used to build them.

In your example, you’ve essentially built your own mini streams library: you defined inputStream, messageSink, and wired everything up manually. If you extracted those functions out, you’d already have the foundation of a proper library. With some refinement, it could actually become quite elegant.

That said, since there isn’t really a high-level library for Web Streams comparable to what RxJS is for Observables, it’s a bit like comparing apples to oranges. The fair comparison would be either native Observables vs Web Streams, or RxJS vs a hypothetical Web Streams-based library.

Very interesting perspective. I’m almost tempted to build a small reactive streams library (something RxJS-like) using Web Streams now.