om-next

keatondunsford 2016-11-01T15:22:55.000309Z

@jasonjckn Wow this is awesome. Do you have support for Docker containers?

2016-11-01T17:59:08.000311Z

i use it with docker, it's a pretty brief Dockerfile

2016-11-01T17:59:14.000312Z

nothing in the project for that

keatondunsford 2016-11-01T18:47:15.000313Z

Awesome. Do you have an example in a repo I could check out?:)

2016-11-01T19:00:29.000314Z

@keatondunsford: I use Duct prodigiously – it’s built on Ring and Compjure. Wouldn’t go back. Ring, as I understand it, is getting async support (if it hasn’t already?), which is Pedestal’s principle advantage. Ring’s advantage is having a wealth of middleware that supports it. And, it’s so simple.

2016-11-01T19:02:59.000315Z

And a side note… If you just have to have Clojurescript on the front-end, personally, I’d try using reagent all on its own, with an upgrade path to re-frame or one of the supporting tools.

2016-11-01T19:03:20.000316Z

@yogthos, I think has made a great case for that path (as opposed to Om): https://www.reddit.com/r/Clojure/comments/2xi4ft/how_to_structurize_a_clojurescriptreagent/

2016-11-01T19:04:15.000318Z

I spent a month working with Om.Next, and frankly, it was hard, and there was too little benefit for the costs.