This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-13
Channels
- # aleph (15)
- # announcements (4)
- # babashka (36)
- # babashka-sci-dev (1)
- # beginners (15)
- # biff (2)
- # calva (15)
- # cider (3)
- # clj-kondo (8)
- # clojure (149)
- # clojure-europe (14)
- # clojure-norway (13)
- # clojure-switzerland (1)
- # clojure-uk (1)
- # clojurescript (21)
- # community-development (5)
- # cursive (20)
- # data-science (2)
- # datomic (7)
- # duct (5)
- # emacs (19)
- # etaoin (3)
- # events (2)
- # fulcro (11)
- # introduce-yourself (2)
- # jobs (4)
- # jobs-discuss (19)
- # joyride (1)
- # leiningen (11)
- # malli (7)
- # membrane (131)
- # nbb (12)
- # nginx (1)
- # off-topic (33)
- # pathom (8)
- # polylith (28)
- # re-frame (8)
- # sci (7)
- # shadow-cljs (225)
- # spacemacs (10)
- # specter (1)
- # vim (10)
- # xtdb (8)
@foo I'm sure I read this at some point in years gone by, but I'd definitely forgotten it: https://rubyonrails.org/doctrine ... thanks for reminding me. Outside of the OOP=yay + MVC=yay and the "Progress over Stability" section, I think it's safe to say I still agree with most of what he's pitching here. One nuance: There's something about Ruby that conflates cute code and beautiful code, but I feel like those battle lines are already well-drawn in the Clojure ecosystem. The first 2 or 3 years of Clojure's existence taught everyone some hard lessons and, in general, I don't see a lot of those painful design mistakes making it very far these days. Clojure is also inherently constrained in a way Ruby isn't, so it's probably not a big deal anyway. Like, Ruby offers 150 weird metaprogramming and object lifecycle hooks that don't even make sense in a Clojure universe.
Yeah it was a good post! I get that impression too. Vaguely reminds me of the behavior of contains?
on vectors.