3 ms·
Pardon my blunt question, but who is the heck is this for? Is this a sideways method of pushing React.js? Or is this for assembly programmers as well, and I jus
by RobertRoberts 9y ago
Pardon my blunt question, but who is the heck is this for? Is this a sideways method of pushing React.js? Or is this for assembly programmers as well, and I just don't get it?
- azangru 9y agoIt has nothing to do with React (in fact, React, despite its name, does not represent the paradigm of reactive programming). This is for javascript programmers who enjoy functional programming and want an introduction into Rx.js library. It may also be of interest for programmers in other languages (because rx has been implemented in many of them).
- c3534l 9y agoI've thought this would be a good way to write video games, but most engines don't support the sort of functional programming that would make this pleasant to use, so I wind up creating events which solve similar kinds of problems. For games, the primary benefit would be to decouple various game components so you can create and remove them without having to worry about a complex web of dependencies and state. It keeps things declarative, which also helps the web of interdependedness problem of many, overlapping systems.