I don't get this paradigm. Maybe it's that particular use, but everything you do is doable using the good old Update callback. I read the UniRx "manifesto" and the one thing that struck me was the example with the double/triple clicks.
You're not wrong here ^^ A callback is an approach to reactive programming done imperatively. Reactive-functional programming therefore is an approach to programming-an abstraction on top of imperative systems-that allows to program asynchronous and event-driven use cases without having to imperatively define the complex interactions of state, particularly across thread and network boundaries. Foremost to avoid the so called callback hell. So, the short answer to what reactive-functional programming is solving is concurrency and parallelism. Hope that helps :)
thanks. very helpful !
very nice tutorial
I don't get this paradigm. Maybe it's that particular use, but everything you do is doable using the good old Update callback. I read the UniRx "manifesto" and the one thing that struck me was the example with the double/triple clicks.
You're not wrong here ^^ A callback is an approach to reactive programming done imperatively. Reactive-functional programming therefore is an approach to programming-an abstraction on top of imperative systems-that allows to program asynchronous and event-driven use cases without having to imperatively define the complex interactions of state, particularly across thread and network boundaries. Foremost to avoid the so called callback hell. So, the short answer to what reactive-functional programming is solving is concurrency and parallelism. Hope that helps :)