This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-09
Channels
- # beginners (22)
- # boot (80)
- # cider (6)
- # cljs-dev (5)
- # clojure (190)
- # clojure-berlin (5)
- # clojure-dev (24)
- # clojure-italy (14)
- # clojure-russia (70)
- # clojure-spec (39)
- # clojure-uk (82)
- # clojurescript (121)
- # clojurewest (1)
- # core-logic (2)
- # cursive (25)
- # datascript (186)
- # datomic (33)
- # dirac (266)
- # emacs (9)
- # gsoc (4)
- # hoplon (37)
- # immutant (34)
- # instaparse (22)
- # jobs (4)
- # juxt (6)
- # lambdaisland (2)
- # leiningen (1)
- # liberator (1)
- # luminus (5)
- # lumo (28)
- # off-topic (9)
- # om (23)
- # onyx (26)
- # other-lisps (1)
- # parinfer (39)
- # pedestal (45)
- # proton (1)
- # protorepl (10)
- # re-frame (18)
- # reagent (4)
- # ring-swagger (8)
- # rum (4)
- # specter (13)
- # test-check (14)
- # testing (1)
- # unrepl (164)
- # untangled (10)
- # yada (14)
Hey all. newbie here. I’m about to get started building a HTTP API with Clojure, and both yada and bidi look neat. The former looks like something you’d use if you want to go all out REST and have great documentation etc, and the latter looks a bit more lightweight and focussed on routing. Is that a fair comparison? Would you recommend one over the other (in general or for specific situations)?
@chillenious Hi! bidi and yada and complementary. Yes, one is just for routing, the other for resources. They work well separately or together
yada knows about bidi so has some additional support for it
Ah, ok. So maybe start with yada and if I need routing that doesn’t quite fit the resources model, use bidi? Or is that overly simplistic?
yada has no router.
You have to combine it with one, like compojure or bidi, but bidi is preferred
ah, ok
I think I got it, thanks
do you intend to keep working on the book for yada?
I mean this one https://leanpub.com/yada 🙂
oh is that generated? ah