In my mind - it comes down to a simple rule of direct dependencies only from view to model/controller (and not the reverse) - the framework just tries to enforce that. The FluxFx stuff is trying to mimic the Redux / React pattern in javascript land (where they have a virtual-dom). Manuel talks about the need for a virtual scenegraph for javafx. I’m not sure the benefit is as large through since afaik the virtual dom is primarily to get around the performance limitations of inherent in the browser dom (although it has other benefits).