This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-29
Channels
- # aleph (1)
- # announcements (10)
- # aws (1)
- # beginners (110)
- # calva (4)
- # cider (26)
- # clj-kondo (14)
- # cljdoc (24)
- # cljsrn (16)
- # clojure (76)
- # clojure-europe (3)
- # clojure-ireland (2)
- # clojure-italy (15)
- # clojure-nl (8)
- # clojure-spec (23)
- # clojure-sweden (4)
- # clojure-uk (92)
- # clojurescript (37)
- # cursive (19)
- # datomic (59)
- # duct (1)
- # emacs (4)
- # fulcro (7)
- # graalvm (7)
- # graphql (1)
- # hoplon (69)
- # jobs (4)
- # jobs-rus (1)
- # kaocha (2)
- # leiningen (5)
- # luminus (2)
- # pathom (8)
- # reagent (6)
- # reitit (11)
- # spacemacs (12)
- # sql (3)
- # tools-deps (9)
- # unrepl (1)
- # vim (57)
You can actually get reitit to play nice with just evaluating your routes again. There is even something in the docs
And if you’re using pedestal, here’s my workaround: https://github.com/metosin/reitit/issues/261#issuecomment-496006361
with component & integrant, the routes can depend on other components, e.g. more routes for dev-mode, generate routes from db. I have a hotkey for integrant reset (& save all files) in Cursive, the reset is subsecond, so quite ok.
btw, some new perf numbers: https://twitter.com/ikitommi/status/1133389851431264256
I'd be interested to see how much mileage you could get/lose if you swapped immutant for aleph
@vale Two of those results already include numbers for Aleph
These plaintext/JSON/single query tests don't really test routing, so they are mostly just benchmark of tuned Immutant server (and Jsonista)
the perf is combination of all. plain-text with slow routing lib is many times slower than with a fast routing lib: the response generation is fast, so the routing dominates.