From bb684c60fd5239dffced7fcd1343e9e033f5a2b1 Mon Sep 17 00:00:00 2001 From: David Nolen Date: Tue, 23 Jan 2024 15:05:05 -0500 Subject: [PATCH] wip --- content/news/2024-01-24-release.adoc | 67 ++++++++++++++++++++++++++++ 1 file changed, 67 insertions(+) create mode 100644 content/news/2024-01-24-release.adoc diff --git a/content/news/2024-01-24-release.adoc b/content/news/2024-01-24-release.adoc new file mode 100644 index 0000000..502f930 --- /dev/null +++ b/content/news/2024-01-24-release.adoc @@ -0,0 +1,67 @@ += 1.11.132 Release +ClojureScript Team +2024-01-24 12:00:00 +:jbake-type: post + +ifdef::env-github,env-browser[:outfilesuffix: .adoc] + +We're happy to announce a new release of ClojureScript. If you're an existing +user of ClojureScript please read over the following release notes carefully. + +This is primarily a bugfix release. + +For a complete list of fixes, changes, and enhancements to ClojureScript see +https://github.com/clojure/clojurescript/blob/master/changes.md#1.11.132[here] + +## Google Closure Compiler & Java 8 + +This will probably be the last ClojureScript release to support Java 8 as Google +Closure Compiler now requires Java 11. + +## Google Closure Library Maintenance Mode & ClojureScript + +Google has [stopped developing Google Closure Library](https://groups.google.com/g/closure-library-discuss/c/FijyNE6_kt4). +What does this mean for the future of ClojureScript? Not a whole lot. Google +Closure Library is a project distinct from the Compiler that provides a large +set of reusable battle-tested libraries that are Closure-compatible. As browsers +and the JavaScript ecosystem have evolved this project has become less +important to Google. + +Google is not going to remove Google Closure Library (GCL) or remove the API +docs or doing anything that would be detrimental to ClojureScript. Note that +Google stopped provided regular releases many years ago - ClojureScript uses an +artifact that we release ourselves. Even if Google did remove GCL from the +Internet, we could still continue to provide the artifact and docs ourselves. + +The standard library, `cljs.core`, uses GCL in relatively simple ways, most of +which could be replaced easily. This will likely happen over time and community +contributions are welcome in this effort. + +The various built-in REPLs (Browser, Node) use a bit more GCL functionality and +could also be evolved gradually over time. + +None of the above changes that we generate Google Closure Compiler compatible +JavaScript and will continue to do so. Google itself embraced the wider +JavaScript ecosystem, but they also transpile everything into Google Closure Compiler +compatible JS (via [tsickle](https://github.com/angular/tsickle)) before finally +processing it with Google Closure Compiler. + +As usual we do not believe in creating meaningless churn for users. You can continue +to rely on GCL in it's current form for years. You can expect various base +GCL namespaces to be available as before. + +Looking towards the future, assessing Google's tsickle strategy for dealing +with JavaScript dependencies is worth assessing deeply. + +## Contributors + +Thanks to all of the community members who contributed to ClojureScript 1.11.51: + +* Will Cohen +* Michiel Borkent +* John Newman +* Enzzo Cavallo +* Allen Rohner +* Adam Kalisz +* Erik Assum +* Nikita Prokopov