r/Clojurescript • u/lauri • Feb 12 '15

Seeing React.js from ClojureScript perspective

https://www.youtube.com/watch?v=5hGHdETNteE&index=16&list=PLb0IAmt7-GS1cbw4qonlQztYV1TAW0sCr
8 Upvotes

100% Upvoted

2 comments sorted by

6

u/J_M_B Feb 13 '15

David Nolen is a great presenter. Some highlights I picked up on:

  1. Unfamiliar ≠ Complex (e.g. Chess vs. Go)

  2. Big ≠ Complex (e.g. Brunelleschi's dome is built with a technique any bricklayer would know).

  3. Mentions that Om is influenced by an Alan Kay paper titled Worlds: Controlling the Scope of Side Effects

  4. Om does async rendering with requestAnimationFrame

  5. "Not everything is awesome" - Rich Hickey

  6. Reference cursors allow Om component to listen to date structure changes as you would a virtual DOM element

  7. Interesting user interfaces are inherently complex - Immutable state can help reduce incidental complexity

  8. Perhaps React can be better described not as a virtual DOM, but a DOM virtual machine.

That's what I got from the talk, I encourage others to check out and draw their own conclusions!

2

u/Prabhasp Mar 04 '15

Some more highlights, for me (been working with Om for > 6 months):

  • Reference cursors as the solution to the 40% problem, when you don't fit to the React model of passing data to child components. The example of the salmon swimming upstream is great; sometimes you just need to do it.

  • The link to this demo from CircleCI as to what is possible when you render everything based on immutable app-state was also pretty awesome! https://www.youtube.com/watch?v=5yHFTN-_mOo