From bb684c60fd5239dffced7fcd1343e9e033f5a2b1 Mon Sep 17 00:00:00 2001 From: David Nolen Date: Tue, 23 Jan 2024 15:05:05 -0500 Subject: [PATCH 1/7] 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 From 42edc491ea8d007befc3a875d6c84b2cb4746379 Mon Sep 17 00:00:00 2001 From: David Nolen Date: Tue, 23 Jan 2024 15:09:58 -0500 Subject: [PATCH 2/7] fix links --- content/news/2024-01-24-release.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/news/2024-01-24-release.adoc b/content/news/2024-01-24-release.adoc index 502f930..5ad3dfb 100644 --- a/content/news/2024-01-24-release.adoc +++ b/content/news/2024-01-24-release.adoc @@ -20,7 +20,7 @@ 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). +Google has https://groups.google.com/g/closure-library-discuss/c/FijyNE6_kt4[stopped developing Google Closure Library]. 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 @@ -43,7 +43,7 @@ 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 +compatible JS (via https://github.com/angular/tsickle[tsickle]) before finally processing it with Google Closure Compiler. As usual we do not believe in creating meaningless churn for users. You can continue From f0f81bf9339473502c12764cbd0bb13df02f3928 Mon Sep 17 00:00:00 2001 From: David Nolen Date: Tue, 23 Jan 2024 15:16:43 -0500 Subject: [PATCH 3/7] tweaks --- content/news/2024-01-24-release.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/news/2024-01-24-release.adoc b/content/news/2024-01-24-release.adoc index 5ad3dfb..81234c0 100644 --- a/content/news/2024-01-24-release.adoc +++ b/content/news/2024-01-24-release.adoc @@ -47,11 +47,12 @@ compatible JS (via https://github.com/angular/tsickle[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. +to rely on GCL in its current form for years. You can expect various base +GCL namespaces (`goog.string`, `goog.object`, etc.) to be available as before. -Looking towards the future, assessing Google's tsickle strategy for dealing -with JavaScript dependencies is worth assessing deeply. +Looking towards the future, it is worth assessing Google's approach with tsickle +to get the benefits of Closure advanced compilation without losing the ease +provided by the JavaScript ecosystem. ## Contributors From b58f96b6fb7402a48095328185841def5036606e Mon Sep 17 00:00:00 2001 From: David Nolen Date: Tue, 23 Jan 2024 15:18:46 -0500 Subject: [PATCH 4/7] tweak --- content/news/2024-01-24-release.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/news/2024-01-24-release.adoc b/content/news/2024-01-24-release.adoc index 81234c0..7c03a5e 100644 --- a/content/news/2024-01-24-release.adoc +++ b/content/news/2024-01-24-release.adoc @@ -46,7 +46,7 @@ JavaScript ecosystem, but they also transpile everything into Google Closure Com compatible JS (via https://github.com/angular/tsickle[tsickle]) before finally processing it with Google Closure Compiler. -As usual we do not believe in creating meaningless churn for users. You can continue +As always, we do not believe in creating meaningless churn for users. You can continue to rely on GCL in its current form for years. You can expect various base GCL namespaces (`goog.string`, `goog.object`, etc.) to be available as before. From 721ff3288cf416ea80446e6cb8e197531ede5624 Mon Sep 17 00:00:00 2001 From: David Nolen Date: Tue, 23 Jan 2024 15:42:12 -0500 Subject: [PATCH 5/7] typo --- content/news/2024-01-24-release.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/news/2024-01-24-release.adoc b/content/news/2024-01-24-release.adoc index 7c03a5e..d1dfc62 100644 --- a/content/news/2024-01-24-release.adoc +++ b/content/news/2024-01-24-release.adoc @@ -56,7 +56,7 @@ provided by the JavaScript ecosystem. ## Contributors -Thanks to all of the community members who contributed to ClojureScript 1.11.51: +Thanks to all of the community members who contributed to ClojureScript 1.11.132: * Will Cohen * Michiel Borkent From 4c9753854798fc475167eca0e8287556b6d3daf0 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Tue, 23 Jan 2024 18:31:50 -0500 Subject: [PATCH 6/7] typos from feedback --- content/news/2024-01-24-release.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/news/2024-01-24-release.adoc b/content/news/2024-01-24-release.adoc index d1dfc62..0111889 100644 --- a/content/news/2024-01-24-release.adoc +++ b/content/news/2024-01-24-release.adoc @@ -27,9 +27,9 @@ 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 +Google is not going to remove Google Closure Library (GCL), remove the API +docs, or doing anything that would be detrimental to ClojureScript. Note that +Google stopped providing 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. From ebe91051dd3bc67943c94cf975bcd6984d2d9489 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Tue, 23 Jan 2024 18:34:07 -0500 Subject: [PATCH 7/7] tweak --- content/news/2024-01-24-release.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/news/2024-01-24-release.adoc b/content/news/2024-01-24-release.adoc index 0111889..5579fcc 100644 --- a/content/news/2024-01-24-release.adoc +++ b/content/news/2024-01-24-release.adoc @@ -24,7 +24,7 @@ Google has https://groups.google.com/g/closure-library-discuss/c/FijyNE6_kt4[sto 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 +and the JavaScript ecosystem have evolved, this project has become less important to Google. Google is not going to remove Google Closure Library (GCL), remove the API