This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-28
Channels
- # announcements (12)
- # babashka (87)
- # beginners (84)
- # calva (22)
- # circleci (4)
- # clj-kondo (46)
- # cljdoc (6)
- # cljsrn (15)
- # clojure (87)
- # clojure-europe (18)
- # clojure-uk (7)
- # clojurescript (20)
- # community-development (3)
- # conjure (1)
- # cursive (13)
- # datomic (14)
- # events (7)
- # fulcro (27)
- # graphql (31)
- # helix (8)
- # jobs-discuss (1)
- # lsp (43)
- # malli (11)
- # meander (64)
- # off-topic (7)
- # pathom (26)
- # polylith (9)
- # practicalli (2)
- # re-frame (33)
- # reagent (2)
- # reitit (5)
- # releases (2)
- # rewrite-clj (2)
- # shadow-cljs (69)
- # specter (5)
- # sql (1)
- # tools-deps (85)
- # tree-sitter (1)
- # vim (3)
Does anyone have/know of a repo that has reagent ssr on graalvm? The only thing I see is https://nextjournal.com/kommen/react-server-side-rendering-with-graalvm-for-clojure, but it uses a fork of cljs
Code splitting for nodejs? Why?
Ah I see! tbd seems like a cool project. Would be very useful to put it on test in AWS Lambda environment!
I don’t yet understand your corespondence with Thomas, since you don’t need code splitting. Nodejs is interpreted, so not loaded libs will not affect startup time. Will read it once again
The point is that when I make a library and expose 10 sub-libraries as one file, that whole file must be loaded
but if I split it into 10 files and 9 of those files can be optionally loaded, then this saves startup time
Oh you mean Clojurescript namespaces?
Unlike clojure, the file size for nodejs is negligible. Nothing happens on runetime. The startup speed is equal to the speed of reading from the hard disk plus interpreting the program itself. "Dead" code is irrelevant.
@U0BBFDED7 reading files takes time. so does interpreting them. I'm not talking about dead code, I'm talking about conditional dependencies
e.g. when you js/require
some code, I don't buy that this is "for free", this always takes some time. it's about minimizing that time.
Dead code, that may be an unfortunate term. I meant that code that is not interpreted costs nothing more than disk read time
Anyway, from what I see on the #shadow-cljs channel, thheller mentioned that the difference probably will be insignificant
I've done some preliminary tests and the difference in startup time are very significant. Even the difference between optimizations simple and advanced are very noticable, let alone when you stuff dozens of extra libraries in there.
We regularly use UIX in projects that we want to use/leverage the very large react ecosystem. You could probably get the tab example working in minutes with UIX.
thats good to hear. I'll give it another shot then
Hey, what would be the best way to create custom SvgIcon components based on some svg files?