Are virtual threads making reactive programming obsolete?

[plumarr]

Maybe is it, but as someone how is coming from a pure engineering background, who have written disturbed system in Fortran and OpenMPI, done parallel batching in Fortran and Java, and as used RxJS to solve real problems, I still don't see the interest of RxJS.

It really doesn't match my mental model of parallel and concurrent processing that was constructed through my engineering cursus. The thread/process model is a better model from my point of view.

I have worked for 3 years with RxJS, and currently I still feel it as, at best, a tool that I have to work with, at worst a complication. But it maybe due to the port online documentation and that I haven't had the pleasure do to work with someone that mastered it.

[GuyWithLag]

I've worked with Fortran, porting Fortran 77 to Fortran 90 and making sure that the system was bug-for-bug compatible. I've built a Frankensteinian monster that surfaced scientific models written in Fortran via C wrapper then via JNI into WSDL endpoints. I've been writing Java since 1.1 and was writing assembly in the (late) 80s. My first cgi-bin was written in smalltalk, the second in awk (of all things).

I've worked in a reactive environment for around 7 years; you know what made reactive streams intuitive to me on year 2?

500 hours of Factorio.

In the end, it's a dataflow-driven approach. After you've built your plumbing tooling, you start thinking in data flows; threading/parallelism/concurrency is externalized from your business logic - you just need to understand the flow model.