> We don't have that right now, and we have no path to having that currently.
We have the same path available to us that DHH had when he built Rails. Ditto for a Commons-style organization that could host a bunch of code. We don't need the core team to lead that initiative any more than 37 Signals needs Matz' or Ruby Central's approval or buy-in to lead an effort and convince people it's worth joining. http://clojurewerkz.org/ is a great start, for example. That's a whole lot of useful, well-documented and actively maintained Clojure code. I agree something like that might be useful, I just don't agree that the Clojure community at large should expect (or desire) all good ideas to be backed or blessed by Cognitect. In other words, people who feel strongly this is worth doing should do it. I suspect the reason there's little momentum here is because it's a lot of exhausting and thankless work.
> Luke got grief for belittling existing community efforts to promote a project he was asking money for.
I must have missed that, and would find it very surprising. I found nothing belittling on this page: https://www.kickstarter.com/projects/1346708779/arachne-rapid-web-development-for-clojure What have I missed? (I would genuinely want to know)...
> Incidentally, Pedestal is pretty hard to get up and running with.
It really isn't: http://pedestal.io/guides/hello-world#_the_whole_shebang
I do agree that it could use much more documentation love. I have contributed some, but could surely do more. That is a separate discussion, however, and pull requests are accepted.
Good mark. AFAIK they mostly do use thread pools (based on the documentation http://pedestal.io/reference/jetty here - you can pass an instance of your custom `ThreadPool` object).
However, this does not detract the fact each handler is maintained in a separate thread (threads), and state is not shared between them. ThreadPool service just makes decisions of which of free threads is to be used
How do you find working with Interceptors?
I'm trying to wrap my head around the concept and find it a bit challenging to think of them in that kind of horseshoe model of execution that's often referenced in the official docs.
It's not that the concept itself is hard to wrap my head around, but I guess the order of an Interceptor chain can seem a bit unintuitive unless you inspect the actual :enter
/:leave
hooks of each individual interceptor.
I've never used Sieppari before, but I found an example of how to use it in the Reitit docs here. However if you're just starting out, you may find Pedestal easier to use, since it takes a more "batteries included" approach. There's a guide for writing a simple API using Pedestal and interceptors here.