-
I think this change is good for them – the manner in which they were using FRP concepts before kind of restricted the utility of it in a way which meant that they were incurring a bunch of conceptual complexity without quite getting to the place where it could fully pay off.
Somewhat ironically, the new Sub (“subscription”) type looks analogous to Event from other FRP systems, albeit with an extremely pared-down API, where their previous Signal type was a sort of unconventional take on Behaviours (with some discrete Event-like aspects mixed in).
It’s really the interplay between Events and Behaviours (through primitives like Reflex’s “hold” and “attach” or reactive-banana’s “stepper” and “apply”) which make FRP so good at expressing things in a way that they can be implemented efficiently, and which allow building libraries of self-contained reusable components which can keep track of their own state.
If you’re not going to have both, you’re probably better off doing something much simpler.
I thought this was known to be a bit cranky?
Surely has more truth to it than the Robert Epstein post. :)
Anyway, if he’s a crank, he’s a very dedicated one. His team has been working on this stuff for quite a few years now, and some of the results seem interesting and promising to me at least.