This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-16
Channels
- # aleph (1)
- # announcements (16)
- # babashka (36)
- # beginners (62)
- # calva (15)
- # cider (21)
- # cljsrn (5)
- # clojure (84)
- # clojure-dev (3)
- # clojure-europe (22)
- # clojure-italy (2)
- # clojure-nl (2)
- # clojure-uk (3)
- # clojurescript (36)
- # core-async (2)
- # cursive (4)
- # datomic (8)
- # emacs (14)
- # events (1)
- # fulcro (4)
- # hyperfiddle (6)
- # introduce-yourself (3)
- # jobs (1)
- # leiningen (4)
- # lsp (100)
- # nrepl (3)
- # off-topic (36)
- # pathom (17)
- # podcasts-discuss (1)
- # polylith (4)
- # portal (14)
- # react (1)
- # reagent (3)
- # reitit (8)
- # releases (3)
- # remote-jobs (1)
- # reveal (7)
- # shadow-cljs (19)
- # sql (16)
- # web-security (3)
More staging area progress. This UI is a pure functional stream expression that emits EAV txs which transact on the server then reflow the reactive UI. See the time basis inc with each tx, proving client/server communication (fully managed by Photon)
👏 Now there's something I can understand 😄 Very tangential, but how are you recording these? It looks really slick!
Not half bad reactive notebook experience - Geoffrey made this test utility in a couple hours
It has been a while since I did a deep dive on Datomic, but ISTR sth about Datomic "pushing" changes to the client. Is that at all involved here? Sorry if that is a dumb question--not really sure what is being demonstrated. But when I saw the bit about pushing changes to the client I started thinking about connecting Cells dataflow to the database, sth I was able to do in Lisp using Franz's persistent CLOS AllegroStore. Super powerful. As you know, come to think of it! 🙂
These images are about Photon, our Clojure dialect for frontend/backend UI with compiler-managed network They are just calling the database repeatedly as the UI changes To do better than that you'd probably want a streaming database like Materialized