> do we want clojure to develop a parallel story for enterprise development I don't think this is feasible, partly because these enterprise frameworks tend to

> do we want clojure to develop a parallel story for enterprise development I don't think this is feasible, partly because these enterprise frameworks tend to be abstract systems, and I haven't seen any evidence in the Clojure world of anyone building anything similar to Quarkus for instance. It's too big a job, we have too few people doing this work in Clojure with the relevant experience to maintain something serious. Much of my thought is put into how do I achieve the standard necessary for my company, and that's where Slipway comes from. But I have to consider how I will also support enterprise grade SAML for instance, and how those lands are shifting, and a number of other similar needs. These are the things that are normally captured by the framework, and those JVM frameworks are moving in a non-Clojurish way. > what do you think can be done on the clojure side to make the slipway integration story easier to reproduce for other enterprise frameworks? Unfortunately I don't have an answer to this, and I'm not sure there is one. Slipway can work with Jetty because Jetty is POJO, and that is becoming more rare in this space. Which would put us back at your first question, 'do we want clojure to develop a parallel story for enterprise development'.