4 ms·
I like FRP, but prefer to imitate it in a synchronous manner now - I mainly work on the JVM and I've personally found debugging to be too painful when working a
by stepbeek 5y ago
I like FRP, but prefer to imitate it in a synchronous manner now - I mainly work on the JVM and I've personally found debugging to be too painful when working asynchronously. If I need async then FRP is definitely the first tool in the toolchest that I'd reach for.
Elixir's pipe operator is a brilliant tool that I wish every language had. I mainly use kotlin day-to-day and definitely abuse the `let` keyword to try to get closer.
- TuringTest 5y agoTrue, FRP doesn't need to be asynchronous; it's just a very good paradigm to support multi-process computation and module composition. As I said above, it just happens to also be a very good at handling state without a fear of side effects.