That's unfortunate because reactive programming shines when you have continuous data flows and want to run pipelines against them; whether that's clicks, websocket events, queue items, etc.

I work with rxjs and its a breeze to work with. My data flow got only complicated after introducing redux-observable.

  document.addEventListener("something", event => { /* blah */ });

is no different.

Nor are Java streams or .NET linq.

Java streams don’t infest your project. They also don’t throw away the error system of the language. They are also leagues more maintainable than a reactive project.

Ignoring the maintenance issues, reactive applications do not yield better performance on realistic I/O-bound workloads: https://julien.ponge.org/blog/publication-performance-and-co...

So all you end up with is less maintainable code and more developer headache.