4 ms·
This looks very interesting -- I don't love the web development story in Clojure/ClojureScript right now, so I'm excited for anything that makes it easier. And
by airlocksoftware 14y ago
This looks very interesting -- I don't love the web development story in Clojure/ClojureScript right now, so I'm excited for anything that makes it easier. And I get that this is an alpha.
That said, one of my biggest pain points with Clojure is poorly documented libraries. This NEEDS a high-level description of what is provided and where, and the example app needs a lot more documentation so I can figure out what it's doing.
EDIT: Whoops, I found the link to the full documentation:
http://pedestal.io/documentation/ http://pedestal.io/documentation/
Much better. I still wish the sample chat app had more documentation, but if I have time I'll try to contribute that myself.
https://github.com/pedestal/samples/tree/master/chat https://github.com/pedestal/samples/tree/master/chat
- rkneufeld 14y agoDuly noted. It's been a real whirlwind getting this stuff out the door in time for Clojure/west and better documentation is one of our major goals following the release. - Ryan @ Relevance
- airlocksoftware 14y agoThanks Ryan. I've read through more of the documentation, and I like what I am seeing. The client-side state management and push rendering looks especially cool. My play Clojure / Clojurescript stack is a weird combination of libraries like Noir (+ Chris Granger's Clojurescript libraries) / Lobos / Korma / Hiccup / stuff I ripped from Clojurescript One. The example explains how to use Datomic with Pedestal, and I notice you're using Domina for DOM manipulation. Is that basically the minimal stack for a database driven app? It'd be nice to see an explanation of what the rest of a Pedestal app might look like, what libraries Pedestal might replace (especially something that integrates with Postgres / MySql). Congrats on the release and a sincere thank you to you guys at Relevance for all of your Clojure work.