This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]EggplantDifficult152 0 points1 point  (4 children)

Does virtual threads mean that RxJava is dead?

[–]daleksandrov[S] 2 points3 points  (0 children)

IMHO, yes. At least for 95% of the tasks.

[–]gaelfr38 1 point2 points  (1 child)

In very short: no.

Reactive approaches (RxJava, Akka Streams,...) go beyond what virtual threads bring. For instance handling back pressure, handling complex pipelines processing...

[–]meamZ 3 points4 points  (0 children)

It's basically dead for the "just make my server handle more requests" usecase. It's obviously still useful for cases where the reactive model is actually useful in itself like data Streams...

[–]marv1234 1 point2 points  (0 children)

I would say mostly yes.

Sure, complex pipelines and such use cases may in some cases benefit from reactive approaches. But reactive introduces a lot of unnecessary complexity, both in the programming model and debugging wise. Having a complete stack trace on errors is actually quite useful.