This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (24)
- # alda (1)
- # aws (10)
- # beginners (15)
- # boot (51)
- # cider (37)
- # clojure (198)
- # clojure-berlin (3)
- # clojure-czech (48)
- # clojure-poland (1)
- # clojure-russia (7)
- # clojure-seattle (1)
- # clojurescript (347)
- # editors (64)
- # emacs (46)
- # hoplon (13)
- # immutant (24)
- # jobs (17)
- # ldnclj (20)
- # ldnproclodo (3)
- # off-topic (8)
- # om (37)
- # onyx (19)
- # re-frame (18)
- # reagent (54)
- # remote-jobs (2)
- # testing (9)
- # yada (1)
- # yleinen (4)
presented with little explanation, but I’m pretty excited about where this is going - feel free to ask questions https://github.com/swannodette/om-next-demo
it includes some things I’ve never talked about before, a sketch on how read/mutation model can be shared between Client Server a la Falcor (this is a huge IMO)
and it shows how trivial is to sync (like zero code), Datomic makes all of this quite trivial
but the model is flexible enough to be purely clientside (i.e. DataScript) or attached to microservices a la Netflix
@akiva ha, not quite there yet - I’m thinking I will probably release an alpha (with copious documentation) so people can help work out the kinks
one the really cool things about the new design is how much you can push mutation / reaction logic into the server
pretty sweet for internal apps where you just want to eliminate the inevitable accidental complexity of doing everything on the client
yeah it’s one read / mutation model you can decide how “far away” you want it to be. Again, all credit to Falcor.
@dnolen Do you foresee any difficulties with a SQL backend other than the slightly more complex parsing to SQL?
Which tools lein/build/figwheel/etc.? How can I build sass? Wondering where to start.
Looks like a sensible place to start. Was getting in a twist working out whether boot or lein was better.
@lukemorton chestnut might be getting behind a bit on latest developments, but at least it's a complete and beginner friendly solution
Make sure to check the docs, and get on the chestnut mailing list if you need any help
Yeah, huge amount of boilerplate though!! To be fair though I just want to try out om and get it live somewhere so cheshnut is perfect.
there's just a bunch of things that have been happening that I haven't had a chance to have a good look at. I'd actually appreciate input in this area on how to improve and evolve Chestnut. Figwheel now comes with its own repl support. Maybe we should be using that? OTOH last time I checked that doesn't work with CIDER, but is weasel still the best option? Another thing, we're including a JS test runner for phantom, I would like to see that go and use doo instead.
the current setup for launching figwheel from the REPL is also a bit hacky, we're duplicating stuff from project.clj which confuses people
the alternatives are parsing it out of there ourselves. Also a hack but at least it's in one place, or launch figwheel with lein-figwheel, instead of from the REPL
I personally don't have all that much RAM on my laptop (4GB), so I try to avoid launching extra java processes. Right now we have figwheel, jetty, repl all in one process which is cool
@afhammad: so this is something that people have misunderstood a bit, there really isn’t any “parsing to SQL"
the router (what’s currently called the “parser”) just dispatches on keys. You can return whatever you want however you want for a key.
@dnolen: ah, I did misunderstand that, thats simple enough. When you said Datomic makes it more trivial, was this in relation to the convenience of :<namespace>/<name> naming and that queries as data are easier to construct?
@afhammad: Datomic’s support for pull syntax just means you can send off a whole subtree to Datomic to takeover