This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-09
Channels
- # aws (51)
- # beginners (57)
- # calva (10)
- # chlorine-clover (7)
- # cider (20)
- # clj-kondo (55)
- # clojure (43)
- # clojure-europe (9)
- # clojure-italy (1)
- # clojure-nl (5)
- # clojure-spec (8)
- # clojure-uk (71)
- # clojurescript (33)
- # core-async (22)
- # cursive (20)
- # datomic (3)
- # emacs (8)
- # figwheel-main (8)
- # fulcro (13)
- # garden (2)
- # graalvm (60)
- # graphql (26)
- # jobs (6)
- # joker (6)
- # kaocha (2)
- # lambdaisland (5)
- # malli (36)
- # off-topic (9)
- # portkey (15)
- # re-frame (3)
- # reagent (25)
- # remote-jobs (4)
- # spacemacs (3)
- # sql (111)
- # tree-sitter (29)
- # uncomplicate (3)
- # xtdb (2)
hello !
mentally playing with an idea on reitit route data -> API GW + handlers to Lambdas... (maybe have :target
keyword on route data for specifying the type of lambda, like jvm, or graal...)
I am a little lost with reitit
compared to other routing libs, any help ?
it represents routes as as via nested vectors, then has ways to compile the routes into fast dispatch via the url path. The leafs of routes can have data attached to them to describe middleware, endpoint handler etc.
compojure
was not good enough ?
reitit can also be used on the frontend, there's a core lib and then bindings to other stuff
compojure is macro heavy, no inspection possible and the standard route matching is O(n) (walks the routes one by one to match for the url path/method)
okay, got it !