4 ms·
You could argue that Clojurescript early adoption of React was one of the reasons for it's rise. The early work of David Nolan (Om) and Dan Holmsand (Cloact->R
by lrenn 5y ago
You could argue that Clojurescript early adoption of React was one of the reasons for it's rise. The early work of David Nolan (Om) and Dan Holmsand (Cloact->Reagent) were, at least in my opinion, pretty influential. Clojure's immutable data structures were (are) a perfect fit. iirc, the fact that "shouldComponentUpdate" could be performant with equality was a huge, easy performance/simplicity win. I may be way off about that, if so, I apologize.
- brundolf 5y agoIt makes well enough sense. I was mainly surprised specifically because this is a game, not a DOM-based web app
- endergen 5y agoThis is how remember things historically.
- erromno 5y agoOm was late, not early, around mid 2015, turned out to be experiment and eventual abandonware. There were much earlier react wrappers, and frameworks like reagent that remain popular today. Dave was influencial in cljs but don't think he ever got a full spa framework off the ground, unless it happened in last few years
- lrenn 5y agoOm came first, Cloact (eventually renamed Reagent due to an unfortunate similarity with a certain body part of a snake) came after it. Here is the original HN post about Cloact: https://news.ycombinator.com/item?id=7037038 https://news.ycombinator.com/item?id=7037038 You can see people comparing it to Om. Here is a blog post of his from 2013 that mentions Om: https://swannodette.github.io/2013/12/31/time-travel/ https://swannodette.github.io/2013/12/31/time-travel/ And yeah, Reagent "won" because it was way simpler but I'd find it hard to believe that it wasn't influence or inspired by Om.
- deleted 5y ago[deleted]
- erromno 5y agoHmm ah okay I meant the write-off omnext, my bad, didn't realize there was previous history, I stand corrected
- dgb23 5y agoFulcro is the successor of OM, a full-stack framework, with some very interesting characteristics and features.
- pharmakom 5y agoYou are right. Equality checks for any complex data-structure in JS (and TypeScript) are cumbersome as hell, yet for a React architecture they are crucial for performance.