This thread over Silk, Bidi and Secretary has been very interesting. I looked 
at the three projects to see how they evolved after this thread started. Any 
cross-pollination or progress worth sharing now that I've missed?

>From what I could gather:

* Secretary is evolving towards a conservative 2.0 and won't, after all, be 
re-implemented on top of Silk. This may be a good thing: not bringing more 
transitive dependencies in all projects using Secretary. Thus, Secretary would 
remain the first stop for Compojure-like easy routing in ClojureScript apps.
* Bidi was already quite mature and comparable to Silk and remains as 
attractive as it was, especially with regard to its established production 
usage and corporate backing.
* Silk's development slowed for some time and this may make for a good occasion 
to reflect on its state and the value of its ambitions (which seemed quite 
interesting to me).
* I would add, from distant memory, that Pedestal's isomorphic routing is 
planned to be extracted into a self-contained library. Judging from the advent 
of Clojure 1.7's reader conditionals and Om's model 2 for which I'm expecting 
an announcement in a few weeks, I suppose Cognitect may start providing again 
their leadership on the front-end. Either they start recommending something 
like Bidi or Silk, or they (more probably) reader-cond-port their routing lib 
to ClojureScript.

I'm watching this space and thanks for any comments.

On Sunday, October 12, 2014 at 11:28:13 PM UTC-4, Dom Kiva-Meyer wrote:
> Thanks for the experience reports, Dylan!
> 
> 
> Colin, Silk is Ring-compatible and meant to be used as a single replacement 
> for both Compojure and Secretary (or any other server/browser routing 
> combination with incompatible syntax and semantics). But, as Dylan said, it's 
> totally fine to use it in conjunction with Compojure instead of replacement. 
> Silk should also work fine with all Ring middleware.
> In the next version, Silk will have a more familiar and mostly 
> Compojure-compatible syntax for defining routes. My hope is that this will 
> make it easier to translate Compojure examples/code to Silk.

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to