This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-08
Channels
- # architecture (20)
- # beginners (140)
- # cider (155)
- # cljsjs (1)
- # cljsrn (29)
- # clojure (53)
- # clojure-dev (9)
- # clojure-italy (40)
- # clojure-nl (13)
- # clojure-poland (4)
- # clojure-russia (8)
- # clojure-uk (51)
- # clojurescript (74)
- # cursive (36)
- # data-science (1)
- # datomic (3)
- # emacs (14)
- # fulcro (11)
- # graphql (2)
- # java (21)
- # javascript (2)
- # jobs (3)
- # nrepl (7)
- # off-topic (18)
- # om-next (1)
- # onyx (9)
- # portkey (8)
- # re-frame (72)
- # reagent (64)
- # reitit (4)
- # remote-jobs (1)
- # rum (1)
- # schema (1)
- # shadow-cljs (49)
- # slack-help (1)
- # spacemacs (8)
- # specter (7)
- # tools-deps (27)
- # vim (28)
@ikitommi, I was an user of compojure-api
, changed jobs and got assigned with a JVM task .. I'm going to use clojure no doubt, but what should I use, reitit or compojure-api? they are both routers that support swagger generation and validation via spec
@plins I think reitit is the future. It's dead simple, clojurescript too, easy to extend, fast and fixes all the issues there has been with c-api. That said, c-api is more proven, 30k monthly downloads. We'll keep on maintaining both. If you don't need to be in prod in next few weeks, I would go with reitit.