This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-24
Channels
- # announcements (1)
- # asami (10)
- # aws (1)
- # babashka (1)
- # beginners (105)
- # cider (13)
- # cljsrn (6)
- # clojure (42)
- # clojure-australia (4)
- # clojure-dev (7)
- # clojure-europe (26)
- # clojure-nl (2)
- # clojure-uk (13)
- # clojurescript (19)
- # code-reviews (3)
- # conjure (18)
- # core-async (4)
- # core-matrix (5)
- # cryogen (3)
- # datomic (27)
- # depstar (21)
- # emacs (2)
- # figwheel-main (9)
- # fulcro (18)
- # helix (7)
- # jobs (3)
- # jobs-discuss (15)
- # juxt (7)
- # kaocha (4)
- # lambdaisland (2)
- # leiningen (11)
- # luminus (1)
- # malli (6)
- # meander (9)
- # minimallist (4)
- # mount (3)
- # off-topic (3)
- # pathom (8)
- # pedestal (28)
- # rdf (13)
- # re-frame (7)
- # reagent (5)
- # shadow-cljs (3)
Good morning early worms!
Holy crap, gzip makes a huge difference! Even though it’s just compressing an unoptimised development build right now, my JS bundle size went from 6.5MB to 889KB. I would never have expected to get that level of compression.
That’s only about 7:1 which is not that unexpected for source code.
Chris Ford has this talk on Kolmogorov sequences in music https://www.youtube.com/watch?v=Qg3XOfioapI
IIRC, the gist of it is that the more compressable something is, the less information it contains.
well, that’s shannon and entropy etc. I would be surprised of music if music would not be compressible well
Well, a musical score achieves a very high compression rate compared to an audio file, doesn't it ? 😉
btw @U04V5VAUN, you triggered me, and now I have to share once again the best textbook on Shannon entropy out there: http://www.inference.org.uk/mackay/itila/
“packaged clojurescript development ring function”?
I’m happy just using shadow-cljs for development-time stuff. I don’t think gzip makes much sense to have on during development.
As simon points out; on local development, bandwidth is not a bottleneck, so adding gzip which takes some amount of processing would likely slow you down
@dominicm I just rely on always having the developer tools open for general observability and defaulting to ✅ disable cache in the network tab (this is in the Chrome developer tools).
@dominicm when you're going down the optimization road, it often makes sense to not have your static artifacts served by your Clojure process at all - e.g leave that to nginx.
@val_waeselynck in production, sure