3 ms·

Notable examples on the desktop: GitHub for Mac (ReactiveCocca) and GitHub for Windows (ReactiveUI) - https://www.youtube.com/watch?v=1XNATGjqM6U https://www.y

Notable examples on the desktop: GitHub for Mac (ReactiveCocca) and GitHub for Windows (ReactiveUI) - https://www.youtube.com/watch?v=1XNATGjqM6U https://www.youtube.com/watch?v=1XNATGjqM6U and https://www.youtube.com/watch?v=HPyKHxy7X0w https://www.youtube.com/watch?v=HPyKHxy7X0w and http://web.archive.org/web/20120714082000/http://www.reactiveui.net/welcome/pdf http://web.archive.org/web/20120714082000/http://www.reactiv... (True Elm is part of the web-community, just saying React was not the first mover but I agree it will certainly be most likely the one that makes FRP cross the chasm)

goldenkey 11y ago
I appreciate your resources, namely the video by the creator of Elm, https://www.youtube.com/watch?v=Agu6jipKfYw https://www.youtube.com/watch?v=Agu6jipKfYw. However, I agree with above poster. I remember developing my first windows app by doing a main event loop. It's been that way for a long time. Only recently are we doing more asychronous callback / bound type mechanisms of reaction. And still not as strong as the FLP stuff mentioned in the video. Not as much functional stuff, just functional paradigms. I personally really like the perfection of static input/output transformation graphs. But yeah..it's not been that way for a while and I agree with OP, the web being so event/input/signal based, has spurred the movement for better ways of reactive programming.