5 ms·

I'm reminded of the Hacker News post that introduced me to React from David Nolen back in 2013, where he first introduced ClojureScript's take on React, Om: ht

by davedx 8y ago

I'm reminded of the Hacker News post that introduced me to React from David Nolen back in 2013, where he first introduced ClojureScript's take on React, Om: http://swannodette.github.io/2013/12/17/the-future-of-javascript-mvcs http://swannodette.github.io/2013/12/17/the-future-of-javasc... Interested to take this for a spin.

masklinn 8y ago
> ClojureScript's take on React, Om His take on React in ClojureScript would probably be a better qualifier, there have been others. Reagent is a popular alternative take on a cljs React interface.
grayrest 8y ago
Om isn't so much a take on React as it is a take on the state management layer and it uses React under the covers. I believe it's been largely superseded by re-frame [1], which follows the Redux / TEA model. There is an Om Next and that's basically a take on Falcor / Relay using the Datomic pull syntax but I haven't heard that much about it outside the talks where he was announcing it. [1] https://github.com/Day8/re-frame/ https://github.com/Day8/re-frame/
- Scarbutt 8y ago
  Why doesn't Clojurescript eliminates the need for something like Redux where Reason does? as mentioned in the article.
  - lilactown 8y ago
    IME using ClojureScript, you don't really need something like Redux/re-frame all that often either. Once you've handled local state and remote data dependencies, you have like 10% of your app state left. That can easily be solved with a global atom (a la re-frame) or something like the new React context API. Our understanding of how to handle state, remote data fetching, etc. has grown a lot over the last few years. Both the React & ClojureScript ecosystem went all-in on global state stores like Redux because, at the time, we thought we needed it. It felt like, if we needed a global state store for one thing, that it made more sense to just put everything in there for cohesiveness. It also was hard to determine up-front what was needed globally (mostly data IME) and what was only needed locally. It turns out that local state and something like apollo/relay/"suspense" for remote data solve the 80-90% case, and now we're getting better tools like React context to handle the last 10%. I don't think that Redux/re-frame is going away, but the number of apps that I would implement with them has gone way down over the years.
radicalnews 8y ago
Fulcro is a full-stack framework that's based on om.next. I've playing around with it for sometime and i feel that it makes the om.next query/mutation model much more easier to use and understand. http://fulcro.fulcrologic.com/ http://fulcro.fulcrologic.com/

by davedx 8y ago

masklinn 8y ago

> ClojureScript's take on React, Om His take on React in ClojureScript would probably be a better qualifier, there have been others. Reagent is a popular alternative take on a cljs React interface.

grayrest 8y ago

Om isn't so much a take on React as it is a take on the state management layer and it uses React under the covers. I believe it's been largely superseded by re-frame [1], which follows the Redux / TEA model. There is an Om Next and that's basically a take on Falcor / Relay using the Datomic pull syntax but I haven't heard that much about it outside the talks where he was announcing it. [1] https://github.com/Day8/re-frame/ https://github.com/Day8/re-frame/

Scarbutt 8y ago
Why doesn't Clojurescript eliminates the need for something like Redux where Reason does? as mentioned in the article.
- lilactown 8y ago
  IME using ClojureScript, you don't really need something like Redux/re-frame all that often either. Once you've handled local state and remote data dependencies, you have like 10% of your app state left. That can easily be solved with a global atom (a la re-frame) or something like the new React context API. Our understanding of how to handle state, remote data fetching, etc. has grown a lot over the last few years. Both the React & ClojureScript ecosystem went all-in on global state stores like Redux because, at the time, we thought we needed it. It felt like, if we needed a global state store for one thing, that it made more sense to just put everything in there for cohesiveness. It also was hard to determine up-front what was needed globally (mostly data IME) and what was only needed locally. It turns out that local state and something like apollo/relay/"suspense" for remote data solve the 80-90% case, and now we're getting better tools like React context to handle the last 10%. I don't think that Redux/re-frame is going away, but the number of apps that I would implement with them has gone way down over the years.

radicalnews 8y ago

Fulcro is a full-stack framework that's based on om.next. I've playing around with it for sometime and i feel that it makes the om.next query/mutation model much more easier to use and understand. http://fulcro.fulcrologic.com/ http://fulcro.fulcrologic.com/