wip

Author: swannodette

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!