This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-04
Channels
- # announcements (13)
- # beginners (51)
- # boot (3)
- # calva (10)
- # cider (20)
- # clj-kondo (55)
- # cljs-dev (60)
- # clojure (99)
- # clojure-europe (6)
- # clojure-gamedev (9)
- # clojure-italy (19)
- # clojure-nl (7)
- # clojure-spec (20)
- # clojure-uk (42)
- # clojurescript (96)
- # clojurex (37)
- # clojutre (1)
- # cursive (37)
- # data-science (2)
- # datomic (15)
- # defnpodcast (9)
- # duct (7)
- # emacs (6)
- # events (9)
- # fulcro (124)
- # jackdaw (4)
- # jobs (4)
- # leiningen (9)
- # malli (7)
- # mount (3)
- # off-topic (109)
- # other-languages (8)
- # re-frame (39)
- # reagent (4)
- # reitit (6)
- # remote-jobs (2)
- # rewrite-clj (36)
- # ring (4)
- # shadow-cljs (16)
- # spacemacs (16)
- # tools-deps (91)
- # vim (8)
- # yada (2)
I've been desperately trying to understand the rationale behind Django and Django REST Framework.
I'd love some pointers to help me see the big picture.
I've read enough of the docs to be able to work with it somewhat. But every once in a while, I come across some problem.
And the only way I get out of that problem is by googling it, and finding something like this on Stack Overflow (or equiv.): "If you're facing <blah>, and you're doing <blah>, you have to create a class inheriting from GenericListAPIViewSet (or some other <blah>) and override method <blah> to do <blah>"
And these recipes work, but I never understand why I needed to do that.
I used yada
to build a webapp and never faced any such problems. There were points where I didn't know/understand some stuff, but all I needed to do was read some docs and I was done.
Building with Django always feels like I'm weaving some monster using already complected concretions instead of composing impls of some well-reasoned abstractions.
Sorry for bloat.