wip

Author: swannodette

content/news/2025-04-24-release.adoc renamed to 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,15 +16,16 @@ 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
 
 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