This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-26
Channels
- # announcements (7)
- # babashka (6)
- # beginners (41)
- # clara (27)
- # clerk (2)
- # cljs-dev (6)
- # clojure (121)
- # clojure-europe (31)
- # clojure-nl (2)
- # clojure-norway (98)
- # clojure-uk (12)
- # clojuredesign-podcast (7)
- # conjure (5)
- # cursive (22)
- # holy-lambda (22)
- # hoplon (9)
- # hyperfiddle (19)
- # leiningen (9)
- # malli (4)
- # music (1)
- # nbb (6)
- # off-topic (10)
- # podcasts-discuss (1)
- # polylith (4)
- # re-frame (2)
- # reitit (2)
- # releases (1)
- # sci (1)
- # shadow-cljs (59)
- # sql (9)
- # vim (41)
- # xtdb (23)
big news, borkdude just ported Javelin to scittle & nbb: https://twitter.com/borkdude/status/1717619707392491753
That was amazing, I asked some questions and then he told me it was already done š
I'm kind of a hoplon noob, but I've heard about it for the first time probably already 10 years ago. How is performance compared to, say, React?
https://tailrecursion.com/~alan/micha_on_hoplon_vs_react/index.html may illuminate
tl;dr
ā¢ problem react solves is needing to necessarily empty out all dom nodes before you add them all back, like if you're syncing an array with a set of elements (like an array to a bunch of todo <li>
ā¢ hoplon solves differently by promoting fine-grained subscriptions to cells. DOM nodes are pooled and reused, no diffing other than clj =
inside javelin
it's basically immediate mode (React) vs. retained mode (Hoplon+Javelin, DOM), in UI speak
