Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
ReactFX vs ReactiveX
Synchronous vs Asynchronous
The key difference from ReactiveX is that event propagation in ReactFX is (almost always) synchronous.
This is consistent with change propagation in JavaFX bindings.
Synchronous event propagation allows for more coordination between event streams, which reduces the number of glitches (temporary inconsistencies in observable state). With ReactiveX, one has to settle for eventual consistency, which in the context of UI programming would frequently result in UI glitches.
Tailored for JavaFX and other single-threaded models
Event propagation in ReactFX stays within one thread (except, obviously, for threadBridge). This means that when an event source produces events on one thread, you don't have to worry that they will be delivered on a different thread. In the context of JavaFX, this means that you don't have to wrap UI manipulating actions in Platform.runLater if the events leading to the action originated from the JavaFX application thread.