Closed serapath closed 8 years ago
I've tried both: Yolk and Cycle both push into the territory of using ReactiveX streams as the basis for your UI components to interact. While I haven't dived into Cycle, it seems to be more 'proper' and formalized system for how everything comes together into your application. For example, it defines the way you sink and pull data from a database or remote service (using drivers). Yolk tends to be less 'opinionated' and leaves much of the structure up to the developer for how these things may work. In practice, Yolk is easier to pick up, but you may end up needing to explore your own solutions for the application structure; while Cycle has a higher learning barrier but has more rigid (yet clear) definitions for how your app is built.
Feel free to correct me @garbles
thx +1
Btw, this is a duplicate of #4
The explanation from @jadbox is pretty on the money. Cycle offers much more structure and encourages "proper" FRP. I'll close this as it looks like you're satisfied with the response.
http://cycle.js.org/
What are the differences?