This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-03
Channels
- # babashka (5)
- # beginners (34)
- # biff (3)
- # calva (29)
- # cherry (11)
- # cider (7)
- # clojure (148)
- # clojure-brasil (1)
- # clojure-europe (16)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-uk (6)
- # clojuredesign-podcast (8)
- # clojurescript (49)
- # cursive (1)
- # datalevin (7)
- # fulcro (1)
- # honeysql (1)
- # jobs (1)
- # matrix (7)
- # off-topic (13)
- # re-frame (12)
- # react (21)
- # reagent (42)
- # releases (6)
- # remote-jobs (2)
- # shadow-cljs (9)
- # solo-full-stack (5)
- # sql (7)
- # squint (9)
- # vim (2)
- # xtdb (11)
- # yamlscript (5)
Working on audio video set up now! And I have almost figured out how to explain the beast!! Drop by in an hour if you like. https://www.meetup.com/london-clojurians/events/296103679/
My pleasure @tschafer! Was I coherent at all? I find presentations hard. 🤯
Oh yes, as a new comer to reactive state management, I can vouch for you making the topic accessible. I was also intrigued by your praise for nodely, as that presentation went over my head to be honest. I’m usually quick with questions, but I didn’t even know what to ask :/
One thing I liked about your slide deck is the list of conceptual reactive capabilities and which frameworks had which.
Those two slides listing reactive capabilities came out of thin air about three hours before the talk! It really helped me understand why I liked MX, and I totally rethought my approach. Everybody manages state! But the D/X...
Nodely was a shock to me. MX builds a DAG behind the scenes, and it was not ever intended! Cells just make note of when other Cells use them...oh look, we have a DAG! :rolling_on_the_floor_laughing: And Nodely starts with a DAG! Intriguing. I need to send Nubank a resume!