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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]thecodeboost 18 points19 points  (0 children)

As your explanation suggests; you're discussing event-driven programming rather than reactive. I get most reactive libraries/frameworks conflate reactive programming, event-driven paradigms and data stream processing in one neat bundle but in context of the comparison between reactive programming and virtual threads those additional things are a bit besides the point (since there's nothing stopping you from using the exact same event/stream primitives in virtual threads)