From c32ddcc042e32bd0e4cb05b358d34036d60a0bfa Mon Sep 17 00:00:00 2001 From: davidnolen Date: Thu, 24 Apr 2025 09:55:27 -0400 Subject: [PATCH 01/15] 2025 release notes wip --- content/news/2025-04-24-release.adoc | 34 ++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 content/news/2025-04-24-release.adoc diff --git a/content/news/2025-04-24-release.adoc b/content/news/2025-04-24-release.adoc new file mode 100644 index 0000000..5ebddce --- /dev/null +++ b/content/news/2025-04-24-release.adoc @@ -0,0 +1,34 @@ += 1.12.35 Release +ClojureScript Team +2024-04-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 release updates Google Closure Compiler to `v20250402` and now depends on the Clojure fork +of Google Closure Library. More on that later. + +For a complete list of fixes, changes, and enhancements to ClojureScript see +https://github.com/clojure/clojurescript/blob/master/changes.md#1.12.35[here] + +## Google Closure Compiler & Java 21 + +Last year we noted that updating Google Closure Compiler would mean losing Java +8 support. Google Closure now requires Java 21. + +## Clojure's Fork of Google Closure Library + +Google stopped contributing to Google Closure Library last August. But +this is largely a blessing in disguise. As far as ClojureScript was +the quality of maintenance for GCL had greatly declined with an +increasing amount of churn over the past five years and Google sorted +out their internal JavaScript strategy. + +## Contributors + +Thanks to all of the community members who contributed to ClojureScript 1.12.35: + +* Will Cohen From 1720304080f697c2a8240e7498b5e62ace921cdc Mon Sep 17 00:00:00 2001 From: davidnolen Date: Thu, 24 Apr 2025 10:19:35 -0400 Subject: [PATCH 02/15] wip, add contributors --- content/news/2025-04-24-release.adoc | 38 ++++++++++++++++++---------- 1 file changed, 24 insertions(+), 14 deletions(-) diff --git a/content/news/2025-04-24-release.adoc b/content/news/2025-04-24-release.adoc index 5ebddce..8adbc4e 100644 --- a/content/news/2025-04-24-release.adoc +++ b/content/news/2025-04-24-release.adoc @@ -5,30 +5,40 @@ ClojureScript Team 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. +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 release updates Google Closure Compiler to `v20250402` and now depends on the Clojure fork -of Google Closure Library. More on that later. +This release updates Google Closure Compiler to `v20250402` and now +depends on the Clojure fork of Google Closure Library. More on that +later. -For a complete list of fixes, changes, and enhancements to ClojureScript see +For a complete list of fixes, changes, and enhancements to +ClojureScript see https://github.com/clojure/clojurescript/blob/master/changes.md#1.12.35[here] ## Google Closure Compiler & Java 21 -Last year we noted that updating Google Closure Compiler would mean losing Java -8 support. Google Closure now requires Java 21. +Last year we noted that updating Google Closure Compiler would mean +losing Java 8 support. Google Closure now requires Java 21. ## Clojure's Fork of Google Closure Library -Google stopped contributing to Google Closure Library last August. But -this is largely a blessing in disguise. As far as ClojureScript was -the quality of maintenance for GCL had greatly declined with an -increasing amount of churn over the past five years and Google sorted -out their internal JavaScript strategy. +Google stopped contributing to Google Closure Library (GCL) last +August. As far as ClojureScript was concerned, the stability of GCL +had declined significantly over the past 5 years with an increasing +amount of churn as Google sorted out their internal JavaScript +strategy. + +We have forked Google Closure Library and have taken up maintenance. +The very first changes made were simply backing out breaking changes +to GCL which have no benefit for ClojureScript and aligning the +codebase with the most recent Google Closure Compiler. ## Contributors -Thanks to all of the community members who contributed to ClojureScript 1.12.35: +Thanks to all of the community members who contributed to +ClojureScript 1.12.35: -* Will Cohen +* Michiel Borkent +* Mike Fikes \ No newline at end of file From f149ad165a0043e2dbd6f91eae0189348149cd34 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Thu, 24 Apr 2025 10:50:30 -0400 Subject: [PATCH 03/15] tweaks --- content/news/2025-04-24-release.adoc | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/content/news/2025-04-24-release.adoc b/content/news/2025-04-24-release.adoc index 8adbc4e..c01994c 100644 --- a/content/news/2025-04-24-release.adoc +++ b/content/news/2025-04-24-release.adoc @@ -9,9 +9,11 @@ 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 release updates Google Closure Compiler to `v20250402` and now -depends on the Clojure fork of Google Closure Library. More on that -later. +This release features two significant dependency changes. First, +Google Closure Compiler has been updated to `v20250402`. This change +makes Java 21 a requirement for ClojureScript. The other signficant +change is that this release now depends on the Clojure fork of Google +Closure Library. More on that later. For a complete list of fixes, changes, and enhancements to ClojureScript see @@ -28,12 +30,13 @@ Google stopped contributing to Google Closure Library (GCL) last August. As far as ClojureScript was concerned, the stability of GCL had declined significantly over the past 5 years with an increasing amount of churn as Google sorted out their internal JavaScript -strategy. +strategy. Google stopping GCL development removes a consistent source +of unexpected surprises between releases. We have forked Google Closure Library and have taken up maintenance. The very first changes made were simply backing out breaking changes -to GCL which have no benefit for ClojureScript and aligning the -codebase with the most recent Google Closure Compiler. +aligning the codebase with the latest Google Closure Compiler +release. ## Contributors From 10850810265b770715cd0c99444939e2b5e6ea31 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Mon, 28 Apr 2025 08:12:25 -0400 Subject: [PATCH 04/15] wip --- content/news/2025-04-24-release.adoc | 41 ++++++++++++++++++---------- 1 file changed, 26 insertions(+), 15 deletions(-) diff --git a/content/news/2025-04-24-release.adoc b/content/news/2025-04-24-release.adoc index c01994c..a961b4f 100644 --- a/content/news/2025-04-24-release.adoc +++ b/content/news/2025-04-24-release.adoc @@ -1,4 +1,4 @@ -= 1.12.35 Release +nh.ki= 1.12.35 Release ClojureScript Team 2024-04-24 12:00:00 :jbake-type: post @@ -11,9 +11,9 @@ notes carefully. This release features two significant dependency changes. First, Google Closure Compiler has been updated to `v20250402`. This change -makes Java 21 a requirement for ClojureScript. The other signficant +makes Java 21 a requirement for ClojureScript. The other significant change is that this release now depends on the Clojure fork of Google -Closure Library. More on that later. +Closure Library. Please read on for more details about these changes. For a complete list of fixes, changes, and enhancements to ClojureScript see @@ -22,21 +22,32 @@ https://github.com/clojure/clojurescript/blob/master/changes.md#1.12.35[here] ## Google Closure Compiler & Java 21 Last year we noted that updating Google Closure Compiler would mean -losing Java 8 support. Google Closure now requires Java 21. +losing Java 8 support. Google Closure now requires Java 21. From our +perspective this change doesn't seem strictly necessary, but Google +is a large organization and this change is probably to due to internal +concerns which are hard to influence from the outside. + +So far, the burden of staying current with Google Closure has been +manageable. If some reason that calculus changes, we could adopt +the strategy we have taken with Google Closure Library. ## Clojure's Fork of Google Closure Library -Google stopped contributing to Google Closure Library (GCL) last -August. As far as ClojureScript was concerned, the stability of GCL -had declined significantly over the past 5 years with an increasing -amount of churn as Google sorted out their internal JavaScript -strategy. Google stopping GCL development removes a consistent source -of unexpected surprises between releases. - -We have forked Google Closure Library and have taken up maintenance. -The very first changes made were simply backing out breaking changes -aligning the codebase with the latest Google Closure Compiler -release. +Google stopped contributing to Google Closure Library (GCL) last August. As far +as ClojureScript is concerned, the stability of certain critical portions of +GCL had declined significantly over the past 5 years. Google was clearly trying +many things with respect to their internal JavaScript strategy, and this churn +surfaced in the stability of the library. Google stopping GCL development +removes a consistent source of unexpected surprises between releases. + +We have forked Google Closure Library and have taken up maintenance. The very +first changes made were simply backing out previously commited breaking changes, +and aligning the codebase with the latest Google Closure Compiler release. + +One of the biggest benefits of GCL is that it makes ClojureScript a complete +solution for writing ClojureScript for a variety of JavaScript contexts. You +don't need to deal with Node modules, build tools, and various flavors of the +month. ## Contributors From 70e68fe89c3ad67211a3ba7ca3ee87f5338d2c78 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Fri, 9 May 2025 21:38:16 -0400 Subject: [PATCH 05/15] wip --- content/news/2025-04-24-release.adoc | 46 +++++++++++++--------------- 1 file changed, 22 insertions(+), 24 deletions(-) diff --git a/content/news/2025-04-24-release.adoc b/content/news/2025-04-24-release.adoc index a961b4f..3a79581 100644 --- a/content/news/2025-04-24-release.adoc +++ b/content/news/2025-04-24-release.adoc @@ -1,19 +1,18 @@ -nh.ki= 1.12.35 Release +nh.ki= 1.12.38 Release ClojureScript Team -2024-04-24 12:00:00 +2024-05-12 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. +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 release features two significant dependency changes. First, -Google Closure Compiler has been updated to `v20250402`. This change -makes Java 21 a requirement for ClojureScript. The other significant -change is that this release now depends on the Clojure fork of Google -Closure Library. Please read on for more details about these changes. +This release features two significant dependency changes. First, Google Closure +Compiler has been updated to `v20250402`. This change makes Java 21 a +requirement for ClojureScript. The other significant change is that this release +now depends on the Clojure fork of Google Closure Library. Please read on for +more details about these changes. For a complete list of fixes, changes, and enhancements to ClojureScript see @@ -21,33 +20,32 @@ https://github.com/clojure/clojurescript/blob/master/changes.md#1.12.35[here] ## Google Closure Compiler & Java 21 -Last year we noted that updating Google Closure Compiler would mean -losing Java 8 support. Google Closure now requires Java 21. From our -perspective this change doesn't seem strictly necessary, but Google -is a large organization and this change is probably to due to internal -concerns which are hard to influence from the outside. +Last year we noted that updating Google Closure Compiler would mean losing Java +8 support. Google Closure now requires Java 21. From our perspective this change +doesn't seem strictly necessary, but Google is a large organization and this +change is likely to due to internal requirements which are hard to influence from +the outside. -So far, the burden of staying current with Google Closure has been -manageable. If some reason that calculus changes, we could adopt -the strategy we have taken with Google Closure Library. +So far, the burden of staying current with Google Closure has been manageable. +If some reason that calculus changes, we could adopt the strategy we have taken +with Google Closure Library. ## Clojure's Fork of Google Closure Library Google stopped contributing to Google Closure Library (GCL) last August. As far -as ClojureScript is concerned, the stability of certain critical portions of +as ClojureScript is concerned, the stability of certain essential portions of GCL had declined significantly over the past 5 years. Google was clearly trying -many things with respect to their internal JavaScript strategy, and this churn -surfaced in the stability of the library. Google stopping GCL development +many things with respect to their internal JavaScript strategy and it showed. Google stopping GCL development removes a consistent source of unexpected surprises between releases. -We have forked Google Closure Library and have taken up maintenance. The very +We have forked Google Closure Library and taken up maintenance. The very first changes made were simply backing out previously commited breaking changes, and aligning the codebase with the latest Google Closure Compiler release. One of the biggest benefits of GCL is that it makes ClojureScript a complete solution for writing ClojureScript for a variety of JavaScript contexts. You -don't need to deal with Node modules, build tools, and various flavors of the -month. +don't need to deal with Node modules and dependencies, build tools, and other +various flavors of the month. ## Contributors From 184b1d89373265c5b033dd9804bbf493c8887aae Mon Sep 17 00:00:00 2001 From: davidnolen Date: Mon, 12 May 2025 09:23:03 -0400 Subject: [PATCH 06/15] wip --- ...4-release.adoc => 2025-05-12-release.adoc} | 29 ++++++++++++------- 1 file changed, 19 insertions(+), 10 deletions(-) rename content/news/{2025-04-24-release.adoc => 2025-05-12-release.adoc} (63%) diff --git a/content/news/2025-04-24-release.adoc b/content/news/2025-05-12-release.adoc similarity index 63% rename from content/news/2025-04-24-release.adoc rename to content/news/2025-05-12-release.adoc index 3a79581..71d79cd 100644 --- a/content/news/2025-04-24-release.adoc +++ b/content/news/2025-05-12-release.adoc @@ -1,4 +1,4 @@ -nh.ki= 1.12.38 Release += 1.12.38 Release ClojureScript Team 2024-05-12 12:00:00 :jbake-type: post @@ -16,7 +16,7 @@ more details about these changes. For a complete list of fixes, changes, and enhancements to ClojureScript see -https://github.com/clojure/clojurescript/blob/master/changes.md#1.12.35[here] +https://github.com/clojure/clojurescript/blob/master/changes.md#1.12.38[here] ## Google Closure Compiler & Java 21 @@ -24,7 +24,8 @@ Last year we noted that updating Google Closure Compiler would mean losing Java 8 support. Google Closure now requires Java 21. From our perspective this change doesn't seem strictly necessary, but Google is a large organization and this change is likely to due to internal requirements which are hard to influence from -the outside. +the outside. The general enthusiasm in the Clojure community about adopting more +recent Java releases hopefully softens the overall impact of this change. So far, the burden of staying current with Google Closure has been manageable. If some reason that calculus changes, we could adopt the strategy we have taken @@ -33,19 +34,27 @@ with Google Closure Library. ## Clojure's Fork of Google Closure Library Google stopped contributing to Google Closure Library (GCL) last August. As far -as ClojureScript is concerned, the stability of certain essential portions of -GCL had declined significantly over the past 5 years. Google was clearly trying -many things with respect to their internal JavaScript strategy and it showed. Google stopping GCL development -removes a consistent source of unexpected surprises between releases. +as ClojureScript is concerned, the stability of GCL had declined significantly +over the past few years after a long period of stability. Google was clearly +trying many things with respect to their internal JavaScript strategy and it +showed. Google ending GCL development removes a consistent source of unexpected +surprises between releases. We have forked Google Closure Library and taken up maintenance. The very first changes made were simply backing out previously commited breaking changes, and aligning the codebase with the latest Google Closure Compiler release. +But why stick with an "aging" JavaScript library? Didn't Google themselves claim +GCL was old-fashioned? Unfortunately for optics, Google avoiding enumerating the +increasingly well-understood costs associated with mainstream JavaScript +development practices. To be fair, this problem permeates contemporary +software industry and highlights the systemic pitfalls that arise from +optimizing ease against other equally valuable properties. + One of the biggest benefits of GCL is that it makes ClojureScript a complete -solution for writing ClojureScript for a variety of JavaScript contexts. You -don't need to deal with Node modules and dependencies, build tools, and other -various flavors of the month. +solution for writing ClojureScript for a variety of JavaScript contexts, +not limited to the browser. You don't need to deal with Node modules and +dependencies, build tools, and other various flavors of the month. ## Contributors From 086cd8108ed6bb927c2b9bbaaa90575ddbe60d1d Mon Sep 17 00:00:00 2001 From: davidnolen Date: Thu, 15 May 2025 09:18:24 -0400 Subject: [PATCH 07/15] wip --- content/news/2025-05-12-release.adoc | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/content/news/2025-05-12-release.adoc b/content/news/2025-05-12-release.adoc index 71d79cd..0b61943 100644 --- a/content/news/2025-05-12-release.adoc +++ b/content/news/2025-05-12-release.adoc @@ -45,21 +45,24 @@ first changes made were simply backing out previously commited breaking changes, and aligning the codebase with the latest Google Closure Compiler release. But why stick with an "aging" JavaScript library? Didn't Google themselves claim -GCL was old-fashioned? Unfortunately for optics, Google avoiding enumerating the -increasingly well-understood costs associated with mainstream JavaScript -development practices. To be fair, this problem permeates contemporary -software industry and highlights the systemic pitfalls that arise from -optimizing ease against other equally valuable properties. +GCL was old-fashioned? Unfortunately, for optics, Google avoided enumerating the +now well-understood costs associated with mainstream JavaScript development +practices. To be perfectly fair to JavaScript, these problems have permeated +the software industry for years and they are cultural, not technical in nature. One of the biggest benefits of GCL is that it makes ClojureScript a complete solution for writing ClojureScript for a variety of JavaScript contexts, not limited to the browser. You don't need to deal with Node modules and -dependencies, build tools, and other various flavors of the month. +dependencies, build tools, build plugins, and other various flavors of the month +to add some interactivity to a website. It rarely matter hows old a dependency +is, take for example `domina`. Sure it generates a bunch of style warning from +the ClojureScript compiler, but it compiles. If not for a Google Closure Library +change you could use the entire API today. ## Contributors Thanks to all of the community members who contributed to -ClojureScript 1.12.35: +ClojureScript 1.12.38: * Michiel Borkent * Mike Fikes \ No newline at end of file From 54736681381f8af9d8ea9456cf858670136cd0ec Mon Sep 17 00:00:00 2001 From: davidnolen Date: Fri, 16 May 2025 00:18:23 -0400 Subject: [PATCH 08/15] wip --- content/news/2025-05-12-release.adoc | 46 ++++++++++++---------------- 1 file changed, 19 insertions(+), 27 deletions(-) diff --git a/content/news/2025-05-12-release.adoc b/content/news/2025-05-12-release.adoc index 0b61943..bca3a42 100644 --- a/content/news/2025-05-12-release.adoc +++ b/content/news/2025-05-12-release.adoc @@ -16,7 +16,7 @@ more details about these changes. For a complete list of fixes, changes, and enhancements to ClojureScript see -https://github.com/clojure/clojurescript/blob/master/changes.md#1.12.38[here] +https://github.com/clojure/clojurescript/blob/master/changes.md#1.12.42[here] ## Google Closure Compiler & Java 21 @@ -28,41 +28,33 @@ the outside. The general enthusiasm in the Clojure community about adopting more recent Java releases hopefully softens the overall impact of this change. So far, the burden of staying current with Google Closure has been manageable. -If some reason that calculus changes, we could adopt the strategy we have taken +If for some reason that calculus changes, we could adopt the strategy we have taken with Google Closure Library. ## Clojure's Fork of Google Closure Library Google stopped contributing to Google Closure Library (GCL) last August. As far as ClojureScript is concerned, the stability of GCL had declined significantly -over the past few years after a long period of stability. Google was clearly -trying many things with respect to their internal JavaScript strategy and it -showed. Google ending GCL development removes a consistent source of unexpected -surprises between releases. +over the past few years after a long period of stability. Google was both +trying many things with respect to their internal JavaScript strategy as +well becoming less concerned about the impact on outside consumers. We have forked Google Closure Library and taken up maintenance. The very first changes made were simply backing out previously commited breaking changes, and aligning the codebase with the latest Google Closure Compiler release. -But why stick with an "aging" JavaScript library? Didn't Google themselves claim -GCL was old-fashioned? Unfortunately, for optics, Google avoided enumerating the -now well-understood costs associated with mainstream JavaScript development -practices. To be perfectly fair to JavaScript, these problems have permeated -the software industry for years and they are cultural, not technical in nature. - One of the biggest benefits of GCL is that it makes ClojureScript a complete -solution for writing ClojureScript for a variety of JavaScript contexts, -not limited to the browser. You don't need to deal with Node modules and -dependencies, build tools, build plugins, and other various flavors of the month -to add some interactivity to a website. It rarely matter hows old a dependency -is, take for example `domina`. Sure it generates a bunch of style warning from -the ClojureScript compiler, but it compiles. If not for a Google Closure Library -change you could use the entire API today. - -## Contributors - -Thanks to all of the community members who contributed to -ClojureScript 1.12.38: - -* Michiel Borkent -* Mike Fikes \ No newline at end of file +solution for writing ClojureScript for a variety of JavaScript contexts, not +limited to the browser. While ClojureScript integrates well with wider JavaScript +ecosystem these days, ClojureScript always provided a solid of set of tools +out of the box as reliable as the standard library. That was true of GCL for a +solid eight years from 2011-2019. + +We working on restoring that stability. With this release, you'll find that quite +a few fine old ClojureScript libraries work again today as well as they did 14 +years ago. + +And for users who are looking for a rich set of functionality but don't need +need to build single page web apps, ClojureScript has a lot to offer without +creating a large final artifact thanks to Google Closure Compiler advanced +optimization. \ No newline at end of file From 0f9ab3c27492e1917fb921fbd8e05923615e1ae1 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Fri, 16 May 2025 00:31:48 -0400 Subject: [PATCH 09/15] wip --- content/news/2025-05-12-release.adoc | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/content/news/2025-05-12-release.adoc b/content/news/2025-05-12-release.adoc index bca3a42..5d056c6 100644 --- a/content/news/2025-05-12-release.adoc +++ b/content/news/2025-05-12-release.adoc @@ -45,16 +45,18 @@ and aligning the codebase with the latest Google Closure Compiler release. One of the biggest benefits of GCL is that it makes ClojureScript a complete solution for writing ClojureScript for a variety of JavaScript contexts, not -limited to the browser. While ClojureScript integrates well with wider JavaScript -ecosystem these days, ClojureScript always provided a solid of set of tools -out of the box as reliable as the standard library. That was true of GCL for a -solid eight years from 2011-2019. - -We working on restoring that stability. With this release, you'll find that quite -a few fine old ClojureScript libraries work again today as well as they did 14 -years ago. - -And for users who are looking for a rich set of functionality but don't need -need to build single page web apps, ClojureScript has a lot to offer without -creating a large final artifact thanks to Google Closure Compiler advanced -optimization. \ No newline at end of file +limited to the browser. These days, ClojureScript integrates well with the wider +JavaScript ecosystem these days, but ClojureScript always provided a solid of set of tools +out of the box as reliable as the standard library. That was absolutely true from +2011-2019 when GCL rigorously avoided breakage. + +We working on restoring that original stability. With this release, you'll find +that quite a few fine old ClojureScript libraries work again today as well as +they did 14 years ago. + +ClojureScript is not just for rich web applications. Many websites need rich +DOM manipulation, robust internationalization, and compelling interactivity on +a website without going to a framework. In these cases ClojureScript +generates surprisingly compact output compared to the JavaScript alternatives.d + +Give it a try! \ No newline at end of file From d343f8bed4ba7bff754dfebc136db6f6e87cff92 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Fri, 16 May 2025 00:32:22 -0400 Subject: [PATCH 10/15] wip --- content/news/2025-05-12-release.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/news/2025-05-12-release.adoc b/content/news/2025-05-12-release.adoc index 5d056c6..5efba0d 100644 --- a/content/news/2025-05-12-release.adoc +++ b/content/news/2025-05-12-release.adoc @@ -1,4 +1,4 @@ -= 1.12.38 Release += 1.12.42 Release ClojureScript Team 2024-05-12 12:00:00 :jbake-type: post From f3e337899e7d0d49eb6ac3699040f81438ea351d Mon Sep 17 00:00:00 2001 From: davidnolen Date: Fri, 16 May 2025 00:35:38 -0400 Subject: [PATCH 11/15] wip --- content/news/2025-05-12-release.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/news/2025-05-12-release.adoc b/content/news/2025-05-12-release.adoc index 5efba0d..e4381f3 100644 --- a/content/news/2025-05-12-release.adoc +++ b/content/news/2025-05-12-release.adoc @@ -48,9 +48,9 @@ solution for writing ClojureScript for a variety of JavaScript contexts, not limited to the browser. These days, ClojureScript integrates well with the wider JavaScript ecosystem these days, but ClojureScript always provided a solid of set of tools out of the box as reliable as the standard library. That was absolutely true from -2011-2019 when GCL rigorously avoided breakage. +2011-2019 when GCL rigorously avoided breaking changes. -We working on restoring that original stability. With this release, you'll find +We are working on restoring that rock solid stability. With this release, you'll find that quite a few fine old ClojureScript libraries work again today as well as they did 14 years ago. From 3da9464287e6821485ca39c6d559bc592f30bbcb Mon Sep 17 00:00:00 2001 From: davidnolen Date: Fri, 16 May 2025 09:30:17 -0400 Subject: [PATCH 12/15] wip --- content/news/2025-05-12-release.adoc | 44 ++++++++++++++-------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/content/news/2025-05-12-release.adoc b/content/news/2025-05-12-release.adoc index e4381f3..69f8905 100644 --- a/content/news/2025-05-12-release.adoc +++ b/content/news/2025-05-12-release.adoc @@ -33,30 +33,30 @@ with Google Closure Library. ## Clojure's Fork of Google Closure Library -Google stopped contributing to Google Closure Library (GCL) last August. As far -as ClojureScript is concerned, the stability of GCL had declined significantly -over the past few years after a long period of stability. Google was both -trying many things with respect to their internal JavaScript strategy as -well becoming less concerned about the impact on outside consumers. +The incredible stability of Google Closure Library started declining around +2019. Google was both trying many things with respect to their internal +JavaScript strategy as well becoming less concerned about the impact on outside +consumers. Finally, Google stopped contributing to Google Closure Library +last August. -We have forked Google Closure Library and taken up maintenance. The very -first changes made were simply backing out previously commited breaking changes, -and aligning the codebase with the latest Google Closure Compiler release. +We have forked Google Closure Library and taken up maintenance. We backed out a +few years of needlees breaking changes and aligned the codebase with the latest +Google Closure Compiler release. One of the biggest benefits of GCL is that it makes ClojureScript a complete -solution for writing ClojureScript for a variety of JavaScript contexts, not -limited to the browser. These days, ClojureScript integrates well with the wider -JavaScript ecosystem these days, but ClojureScript always provided a solid of set of tools -out of the box as reliable as the standard library. That was absolutely true from -2011-2019 when GCL rigorously avoided breaking changes. - -We are working on restoring that rock solid stability. With this release, you'll find -that quite a few fine old ClojureScript libraries work again today as well as -they did 14 years ago. - -ClojureScript is not just for rich web applications. Many websites need rich -DOM manipulation, robust internationalization, and compelling interactivity on -a website without going to a framework. In these cases ClojureScript -generates surprisingly compact output compared to the JavaScript alternatives.d +solution for a variety of JavaScript contexts, not limited to the browser. +Taking on additional dependencies always comes with a cost. One of +ClojureScript's original value propositions was a rock solid set of standard +JavaScript tool as dependable as `clojure.core`. + +We are working on restoring that rock solid stability. With this release, you'll +find that quite a few fine old ClojureScript libraries work again today as well +as they did 14 years ago. + +ClojureScript is and never was only just for rich web applications. Even in the +post React-world, most of the web is (sensibly) still using jQuery. If you need +non-trivial DOM manipulation, robust internationalization, and compelling +interactivity without a framework, ClojureScript works well and generates +surprisingly compact output compared to the JavaScript alternatives. Give it a try! \ No newline at end of file From e3655b9fdbf66e5cce90310f16be977316dc2c32 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Fri, 16 May 2025 11:56:11 -0400 Subject: [PATCH 13/15] wip --- ...-05-12-release.adoc => 2025-05-16-release.adoc} | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) rename content/news/{2025-05-12-release.adoc => 2025-05-16-release.adoc} (86%) diff --git a/content/news/2025-05-12-release.adoc b/content/news/2025-05-16-release.adoc similarity index 86% rename from content/news/2025-05-12-release.adoc rename to content/news/2025-05-16-release.adoc index 69f8905..5d5f8d1 100644 --- a/content/news/2025-05-12-release.adoc +++ b/content/news/2025-05-16-release.adoc @@ -1,6 +1,6 @@ = 1.12.42 Release ClojureScript Team -2024-05-12 12:00:00 +2024-05-16 12:00:00 :jbake-type: post ifdef::env-github,env-browser[:outfilesuffix: .adoc] @@ -46,8 +46,8 @@ Google Closure Compiler release. One of the biggest benefits of GCL is that it makes ClojureScript a complete solution for a variety of JavaScript contexts, not limited to the browser. Taking on additional dependencies always comes with a cost. One of -ClojureScript's original value propositions was a rock solid set of standard -JavaScript tool as dependable as `clojure.core`. +ClojureScript's original value propositions was a rock solid set of readily +available JavaScript tools as dependable as `clojure.core`. We are working on restoring that rock solid stability. With this release, you'll find that quite a few fine old ClojureScript libraries work again today as well @@ -55,8 +55,10 @@ as they did 14 years ago. ClojureScript is and never was only just for rich web applications. Even in the post React-world, most of the web is (sensibly) still using jQuery. If you need -non-trivial DOM manipulation, robust internationalization, and compelling -interactivity without a framework, ClojureScript works well and generates -surprisingly compact output compared to the JavaScript alternatives. +non-trivial DOM manipulation, robust internationalization, data/time, color +value manipulation, mathematics, programmatic animation, browser history, +accessibility helpers, graphics, and more, all without committing to a framework +and without bloating your final JavaScript artifact - ClojureScript is a one +stop shop. Give it a try! \ No newline at end of file From 3d5fa61e9c7819abdd3d715d511c51c0d98a1489 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Fri, 16 May 2025 15:46:38 -0400 Subject: [PATCH 14/15] wrapping up --- content/news/2025-05-16-release.adoc | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/content/news/2025-05-16-release.adoc b/content/news/2025-05-16-release.adoc index 5d5f8d1..8976fa8 100644 --- a/content/news/2025-05-16-release.adoc +++ b/content/news/2025-05-16-release.adoc @@ -24,7 +24,7 @@ Last year we noted that updating Google Closure Compiler would mean losing Java 8 support. Google Closure now requires Java 21. From our perspective this change doesn't seem strictly necessary, but Google is a large organization and this change is likely to due to internal requirements which are hard to influence from -the outside. The general enthusiasm in the Clojure community about adopting more +the outside. The general enthusiasm in the Clojure community around adopting more recent Java releases hopefully softens the overall impact of this change. So far, the burden of staying current with Google Closure has been manageable. @@ -39,8 +39,8 @@ JavaScript strategy as well becoming less concerned about the impact on outside consumers. Finally, Google stopped contributing to Google Closure Library last August. -We have forked Google Closure Library and taken up maintenance. We backed out a -few years of needlees breaking changes and aligned the codebase with the latest +We have forked Google Closure Library (GCL) and taken up maintenance. We backed out a +few years of needless breaking changes and aligned the codebase with the latest Google Closure Compiler release. One of the biggest benefits of GCL is that it makes ClojureScript a complete @@ -49,15 +49,15 @@ Taking on additional dependencies always comes with a cost. One of ClojureScript's original value propositions was a rock solid set of readily available JavaScript tools as dependable as `clojure.core`. -We are working on restoring that rock solid stability. With this release, you'll -find that quite a few fine old ClojureScript libraries work again today as well -as they did 14 years ago. +We are working on restoring that original stability. With this release, you'll +find that quite a few old ClojureScript libraries work again today as well +as they did *14 years* ago. ClojureScript is and never was only just for rich web applications. Even in the -post React-world, most of the web is (sensibly) still using jQuery. If you need -non-trivial DOM manipulation, robust internationalization, data/time, color -value manipulation, mathematics, programmatic animation, browser history, -accessibility helpers, graphics, and more, all without committing to a framework +post React-world, a large portion of the web is (sensibly) still using jQuery. If you need +robust DOM manipulation, internationalization, date/time handling, color +value manipulation, mathematics, programmatic animation, browser history management, +accessibility support, graphics, and much more, all without committing to a framework and without bloating your final JavaScript artifact - ClojureScript is a one stop shop. From 3ec4b8971626202dd9a416e99abf32e37c8e6e25 Mon Sep 17 00:00:00 2001 From: davidnolen Date: Fri, 16 May 2025 15:48:35 -0400 Subject: [PATCH 15/15] tweak --- content/news/2025-05-16-release.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/news/2025-05-16-release.adoc b/content/news/2025-05-16-release.adoc index 8976fa8..9ff1d1d 100644 --- a/content/news/2025-05-16-release.adoc +++ b/content/news/2025-05-16-release.adoc @@ -1,6 +1,6 @@ = 1.12.42 Release ClojureScript Team -2024-05-16 12:00:00 +2024-05-16 16:00:00 :jbake-type: post ifdef::env-github,env-browser[:outfilesuffix: .adoc]