Skip to content

Commit 13b4318

Browse files
authored
Release Spring 2025 (#417)
* 2025 release notes
1 parent 2f2ee7a commit 13b4318

File tree

1 file changed

+64
-0
lines changed

1 file changed

+64
-0
lines changed

content/news/2025-05-16-release.adoc

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
= 1.12.42 Release
2+
ClojureScript Team
3+
2024-05-16 16:00:00
4+
:jbake-type: post
5+
6+
ifdef::env-github,env-browser[:outfilesuffix: .adoc]
7+
8+
We're happy to announce a new release of ClojureScript. If you're an existing
9+
user of ClojureScript please read over the following release notes carefully.
10+
11+
This release features two significant dependency changes. First, Google Closure
12+
Compiler has been updated to `v20250402`. This change makes Java 21 a
13+
requirement for ClojureScript. The other significant change is that this release
14+
now depends on the Clojure fork of Google Closure Library. Please read on for
15+
more details about these changes.
16+
17+
For a complete list of fixes, changes, and enhancements to
18+
ClojureScript see
19+
https://github.com/clojure/clojurescript/blob/master/changes.md#1.12.42[here]
20+
21+
## Google Closure Compiler & Java 21
22+
23+
Last year we noted that updating Google Closure Compiler would mean losing Java
24+
8 support. Google Closure now requires Java 21. From our perspective this change
25+
doesn't seem strictly necessary, but Google is a large organization and this
26+
change is likely to due to internal requirements which are hard to influence from
27+
the outside. The general enthusiasm in the Clojure community around adopting more
28+
recent Java releases hopefully softens the overall impact of this change.
29+
30+
So far, the burden of staying current with Google Closure has been manageable.
31+
If for some reason that calculus changes, we could adopt the strategy we have taken
32+
with Google Closure Library.
33+
34+
## Clojure's Fork of Google Closure Library
35+
36+
The incredible stability of Google Closure Library started declining around
37+
2019. Google was both trying many things with respect to their internal
38+
JavaScript strategy as well becoming less concerned about the impact on outside
39+
consumers. Finally, Google stopped contributing to Google Closure Library
40+
last August.
41+
42+
We have forked Google Closure Library (GCL) and taken up maintenance. We backed out a
43+
few years of needless breaking changes and aligned the codebase with the latest
44+
Google Closure Compiler release.
45+
46+
One of the biggest benefits of GCL is that it makes ClojureScript a complete
47+
solution for a variety of JavaScript contexts, not limited to the browser.
48+
Taking on additional dependencies always comes with a cost. One of
49+
ClojureScript's original value propositions was a rock solid set of readily
50+
available JavaScript tools as dependable as `clojure.core`.
51+
52+
We are working on restoring that original stability. With this release, you'll
53+
find that quite a few old ClojureScript libraries work again today as well
54+
as they did *14 years* ago.
55+
56+
ClojureScript is and never was only just for rich web applications. Even in the
57+
post React-world, a large portion of the web is (sensibly) still using jQuery. If you need
58+
robust DOM manipulation, internationalization, date/time handling, color
59+
value manipulation, mathematics, programmatic animation, browser history management,
60+
accessibility support, graphics, and much more, all without committing to a framework
61+
and without bloating your final JavaScript artifact - ClojureScript is a one
62+
stop shop.
63+
64+
Give it a try!

0 commit comments

Comments
 (0)