This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-22
Channels
- # architecture (9)
- # beginners (90)
- # cider (98)
- # cljs-dev (23)
- # cljsrn (4)
- # clojure (101)
- # clojure-brasil (3)
- # clojure-dev (48)
- # clojure-italy (15)
- # clojure-losangeles (3)
- # clojure-russia (12)
- # clojure-uk (17)
- # clojured (1)
- # clojurescript (141)
- # community-development (15)
- # core-async (1)
- # datascript (12)
- # datomic (18)
- # docker (3)
- # emacs (1)
- # events (1)
- # figwheel (1)
- # fulcro (57)
- # graphql (4)
- # javascript (9)
- # jobs (1)
- # lein-figwheel (1)
- # leiningen (1)
- # lumo (1)
- # off-topic (68)
- # om (9)
- # om-next (3)
- # onyx (4)
- # parinfer (6)
- # pedestal (14)
- # portkey (2)
- # proton (1)
- # protorepl (19)
- # re-frame (57)
- # reagent (46)
- # ring-swagger (12)
- # shadow-cljs (167)
- # slack-help (5)
- # specter (18)
- # sql (1)
- # uncomplicate (3)
- # unrepl (1)
@faxa pretty big architecturally. More like a different project than a new version of om. This link describes differences pretty nicely https://circleci.com/blog/why-we-use-om-and-why-were-excited-for-om-next/
my boss wants me to use OM but not OM-Nextbut. I can see OM project in general almost staled in development...
@faxa Yep. Om is pretty stable from what I know, might be a good call if it's not a big project. But yep the focus has shifted to om-next. Om-next on the other hand is awesome conceptually but really flexible and you need to write a lot of stuff it's not an "out of the box solution", it's more of a blueprint đŸ™‚ the learning curve is pretty huge for om-next and the're not many resources available.
There's Fulcro (https://github.com/fulcrologic/fulcro) which has a lot of documentation and started as a library on top of Om Next
They have a channel here as well
I wouldn't recommend using Om current for a new development