This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-10
Channels
- # announcements (9)
- # aws (11)
- # babashka (37)
- # beginners (97)
- # biff (2)
- # calva (73)
- # clj-kondo (17)
- # cljfx (3)
- # clojure (89)
- # clojure-europe (45)
- # clojure-norway (12)
- # clojurescript (17)
- # datahike (8)
- # datomic (13)
- # deps-new (4)
- # figwheel-main (1)
- # graalvm (2)
- # hyperfiddle (8)
- # introduce-yourself (6)
- # leiningen (38)
- # lsp (57)
- # malli (13)
- # nbb (46)
- # off-topic (40)
- # pathom (3)
- # polylith (8)
- # rum (4)
- # shadow-cljs (14)
- # spacemacs (1)
- # sql (11)
- # xtdb (10)
What are some considerations for when rum/defc
cannot pre-compile the hiccup defined within a component? We're looking to minimize the amount of hiccup intrepretation at runtime. Any helpful hints on building a better intuition around this?
from https://github.com/tonsky/rum/blob/9feb2a1781e3ef716361f9788150a01ea7f791b6/doc/optimizations.md
> In Rum for example, where most of the Hiccup is pre-compiled into React calls via defc
macro the perf hit is lower than in Reagent, thus the possibility of usefulness of memoization is lower.
Maybe @U0FR82FU1 can comment?
Thanks Niki. Roman, let me know if you're able to provide any insight here If I'm understanding this https://github.com/tonsky/rum/blob/0.12.9/src/daiquiri/compiler.clj#L134 correctly, lots of forms are pre-compiled. What are the common exceptions to this?
Ooh, I found some more helpful info here: https://github.com/tonsky/rum/blob/gh-pages/README.md#performance
I'll flip the compiler flag on to get some hints as well: (rum.core/set-warn-on-interpretation! true)
I think I"m all set, ty!