This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-08-02
Channels
- # announcements (6)
- # beginners (35)
- # calva (5)
- # cider (3)
- # clj-http (1)
- # clj-kondo (52)
- # clojure (51)
- # clojure-conj (2)
- # clojure-europe (28)
- # clojure-losangeles (1)
- # clojure-norway (8)
- # clojure-uk (2)
- # cursive (12)
- # datalevin (2)
- # datomic (38)
- # emacs (7)
- # events (5)
- # gratitude (1)
- # humbleui (7)
- # hyperfiddle (23)
- # jobs (1)
- # off-topic (6)
- # portland-or (1)
- # rdf (3)
- # releases (2)
- # xtdb (3)
Looks like GCL is officially stable software now 😛 https://github.com/google/closure-library
The closure compiler is not being deprecated though. And it seems everything j2cl is using from the closure library will move either in j2cl or clojure-compiler. Probably ClojureScript can still rely on clojure compiler then...
This is exactly what the cljs folks have said: the compiler is staying maintained but the library is going away... And very little in cljs relies on the library. This isn't news, right?
I had forgotten GCL was supposed to be sunset at all. Plenty of libraries in CLJS I use end up wrapping some functionality exposed by GCL. This isnt a problem because the code just works and one doesnt have to depend on GCL to use ClojureScript anyway. My joke regarding GCL becoming “stable software” is that the ClojureScript maintainers no longer have to worry about Google randomly breaking things between commits (often without warning). In that sense, GCL is now more stable than its ever been!