4 ms·
That's also because they exist in a browser. The browser displays one page (from the viewpoint of a web app) and has one global event loop, the event loop calls
by Scarblac 3y ago
That's also because they exist in a browser. The browser displays one page (from the viewpoint of a web app) and has one global event loop, the event loop calls into the application code. Application code doesn't run at other times. Reactive programming is a good fit for that.
- PaulDavisThe1st 3y ago> one global event loop, the event loop calls into the application code. Application code doesn't run at other times. In the 80s we called that "event-driven programming", and until threads became widely available, it is how all native GUI programming worked, more or less.
- marcosdumay 3y agoEvent-driven is the "reactive" part only. And the old implementations of it where so less capable of fine-handling the events and complex dependencies that it's reasonable to change the name.
- PaulDavisThe1st 3y agoI would disagree. Conventional desktop GUI toolkits offer much more fine-handling of events and complex event/data dependencies. Web front ends are now approaching those levels, though from a different direction.