This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-15
Channels
- # announcements (7)
- # aws (30)
- # beginners (141)
- # boot-dev (3)
- # cider (48)
- # clara (35)
- # clojure (94)
- # clojure-europe (6)
- # clojure-italy (20)
- # clojure-nl (19)
- # clojure-norway (1)
- # clojure-portugal (6)
- # clojure-spec (7)
- # clojure-survey (3)
- # clojure-uk (93)
- # clojuredesign-podcast (22)
- # clojurescript (20)
- # core-async (54)
- # cursive (29)
- # datascript (1)
- # datomic (4)
- # emacs (2)
- # fulcro (10)
- # jobs (17)
- # juxt (3)
- # kaocha (20)
- # leiningen (20)
- # malli (22)
- # other-languages (7)
- # pedestal (4)
- # perun (2)
- # quil (2)
- # re-frame (7)
- # reagent (3)
- # reitit (31)
- # shadow-cljs (18)
- # spacemacs (11)
- # vim (32)
Just listened to your first episode of the Web Series - looking forward to the next
I use reitit as my choice of framework. My use case is receiving GraphQL requests (just normal RESTful requests) as JSON, doing parsing etc.., business logic.
I'm quite a newbie at Clojure so it was quite a learning experience (I'm coming from (still use) Spring Boot with Kotlin, and that's super easy))
Very interesting. I'm curious as to why it is easier in Kotlin. Are there fewer choices? Does the community rally around one stack?
Not sure, but with Spring Boot it's as simple as adding a dependency at annotating one class. Writing a RESTful controller is again just annotating one class (with one annotation).