This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-04
Channels
- # announcements (5)
- # babashka (2)
- # beginners (53)
- # biff (11)
- # calva (5)
- # cider (4)
- # clojure (32)
- # clojure-austin (2)
- # clojure-dev (5)
- # clojure-europe (17)
- # clojure-norway (22)
- # clojurescript (23)
- # core-logic (1)
- # cryogen (1)
- # datomic (1)
- # dev-tooling (7)
- # emacs (6)
- # fulcro (63)
- # guix (1)
- # hyperfiddle (14)
- # integrant (2)
- # lsp (6)
- # missionary (4)
- # nbb (42)
- # overtone (9)
- # reitit (8)
- # specter (3)
- # sql (2)
- # squint (7)
- # tools-build (9)
Hello, 👋 I'm new to squint. I think I understand the main offer: more js, less clj(s). I can easily understand why js interops will be easier, why the bundle will be smaller and why in some cases there will be performance gains. But I'm curious about the cost of moving away from the cljs ecosystem, what are the implications for using libraries like, say, specter / reagent... P.S I think I also read somewhere about implications on the REPL, so a word about that will be appropriated ☺️
Yes, squint is mostly for places where you mostly need JS and not the CLJS specific libraries.
REPL is a work in progress, there is a console REPL, I have nREPL in a branch but not done yet. For front-end I mostly recommend using vite hot reloading
is there a straight forward way to use cljs libs?
and what is the parity with the cljs.core lib? do we have things like protocols, multimethods?