Skip to content

Commit aca4a63

Browse files
authored
January 2024 Release (#412)
* Januaray 2024 release notes
1 parent 0c60e5d commit aca4a63

File tree

1 file changed

+68
-0
lines changed

1 file changed

+68
-0
lines changed

content/news/2024-01-24-release.adoc

+68
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
= 1.11.132 Release
2+
ClojureScript Team
3+
2024-01-24 12: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 is primarily a bugfix release.
12+
13+
For a complete list of fixes, changes, and enhancements to ClojureScript see
14+
https://github.com/clojure/clojurescript/blob/master/changes.md#1.11.132[here]
15+
16+
## Google Closure Compiler & Java 8
17+
18+
This will probably be the last ClojureScript release to support Java 8 as Google
19+
Closure Compiler now requires Java 11.
20+
21+
## Google Closure Library Maintenance Mode & ClojureScript
22+
23+
Google has https://groups.google.com/g/closure-library-discuss/c/FijyNE6_kt4[stopped developing Google Closure Library].
24+
What does this mean for the future of ClojureScript? Not a whole lot. Google
25+
Closure Library is a project distinct from the Compiler that provides a large
26+
set of reusable battle-tested libraries that are Closure-compatible. As browsers
27+
and the JavaScript ecosystem have evolved, this project has become less
28+
important to Google.
29+
30+
Google is not going to remove Google Closure Library (GCL), remove the API
31+
docs, or doing anything that would be detrimental to ClojureScript. Note that
32+
Google stopped providing regular releases many years ago - ClojureScript uses an
33+
artifact that we release ourselves. Even if Google did remove GCL from the
34+
Internet, we could still continue to provide the artifact and docs ourselves.
35+
36+
The standard library, `cljs.core`, uses GCL in relatively simple ways, most of
37+
which could be replaced easily. This will likely happen over time and community
38+
contributions are welcome in this effort.
39+
40+
The various built-in REPLs (Browser, Node) use a bit more GCL functionality and
41+
could also be evolved gradually over time.
42+
43+
None of the above changes that we generate Google Closure Compiler compatible
44+
JavaScript and will continue to do so. Google itself embraced the wider
45+
JavaScript ecosystem, but they also transpile everything into Google Closure Compiler
46+
compatible JS (via https://github.com/angular/tsickle[tsickle]) before finally
47+
processing it with Google Closure Compiler.
48+
49+
As always, we do not believe in creating meaningless churn for users. You can continue
50+
to rely on GCL in its current form for years. You can expect various base
51+
GCL namespaces (`goog.string`, `goog.object`, etc.) to be available as before.
52+
53+
Looking towards the future, it is worth assessing Google's approach with tsickle
54+
to get the benefits of Closure advanced compilation without losing the ease
55+
provided by the JavaScript ecosystem.
56+
57+
## Contributors
58+
59+
Thanks to all of the community members who contributed to ClojureScript 1.11.132:
60+
61+
* Will Cohen
62+
* Michiel Borkent
63+
* John Newman
64+
* Enzzo Cavallo
65+
* Allen Rohner
66+
* Adam Kalisz
67+
* Erik Assum
68+
* Nikita Prokopov

0 commit comments

Comments
 (0)