Fork me on GitHub

one more change for code splitting guide


looking at bumping Closure to prep for next release


if there's anything important you all think I should look at now is the time


Any ticket? would be great to fix IMO. Clearly a bunch of effort has gone in to data_literals.cljc already and hopefully not much more would be required to make it work


@alexmiller building google-closure-library would need a release of that as well


(unless that's automated now)


@alexmiller re: site needs another bump -- missed clj --main ...

Alex Miller (Clojure team)16:05:05

will build google-closure


I triggered the build, just needs release steps - thanks!

Alex Miller (Clojure team)16:05:43

yeah, I missed that and redid it :)

Alex Miller (Clojure team)16:05:59

I just released though, will take 10-15m to show up

Alex Miller (Clojure team)17:05:58

org.clojure/google-closure-library 0.0-20210512-04d6fb3b org.clojure/google-closure-library-third-party 0.0-20210512-04d6fb3b


@alexmiller looks like Google Closure Lib is now broken for how we consume it - a battle for another day


The stability of Closure Compiler and Lib has really fallen low


do you mean it's buggy in the manner used in cljs or conceptually is moving away from the way cljs uses it?


No just that everytime I’ve bumped in the past two years stuff is broken


They don’t use semantic versioning but they also change stuff


We’re somewhat unique consumers but I’m not even so sure about that


My impression was that other users of Closure depend on some details as well for custom building


glib also has a lot of low value refactoring


Or perhaps can’t see how it could matter


Switching to ES6 classes and goog modules before


@alexmiller that's interesting but probably incomplete? If we could get them in JIRA could help them take that past the finish line

Alex Miller (Clojure team)18:05:19

I can fix them up, sounds like they have a CA already

Alex Miller (Clojure team)18:05:36

(although I always wonder why people have more than 20 parameters :)


perhaps a macro generated it?

Alex Miller (Clojure team)18:05:19

"If you have a procedure with 10 parameters, you probably missed some." - Alan Perlis

😆 8

I think bumping glib for next release is probably more trouble than it's worth - who knows what lurks beneath - can save it for later


Again feel free to propose other tickets worth considering


@alexmiller Windows support for clojure tool is pretty good now yes?


The main problems with it are: it's powershell, so shelling out to it from, say, Java, or nodeJS, or whatever editor is problematic, as it's not a normal process you can start. Another problem is that it doesn't work from cmd.exe, as you always need to go through powershell first.

borkdude19:05:59 solves some of these (in fairness, niche, because Windows usage is already niche in Clojure land) problems by providing a binary* instead which is a drop-in replacement for the official Clojure CLI *(or uberjar, or babashka script)


@pez can probably tell you more from the editor integration side, as he dealt with a fair share of Windows people lately


In general the -X style invocation causes some headaches for Windows users especially because quoting strings is pretty confusing in both cmd.exe and powershell


There's also #clj-on-windows if you want to know more.

Alex Miller (Clojure team)19:05:54

I think that is a fair accounting


Probably for the most mainstream usage it works well, this must also be said. People for whom it works well, are the ones you never hear from ;)


@dnolen on the Windows topic: way back I worked making I think you safely close this issue as stale. Would probably suggest rewriting bash scripts in Clojure if revisiting - and run through babashka or clojure.


Another problem on Windows is that the java.exe that Oracle’s installer makes the default, borks double quoting (strips double quotes fully and totally) . So any invokation of clojure using that java.exe, involving double quoting anything, will fail. This since JDK11. See


This is regardless of powershell or cmd.exe and hits deps.clj as well.


@dnolen If you are house-cleaning old issues, feel free to closeout too (kinda tied to Windows bash script work).


@dnolen unrelated to Windows, but while I’m looking at CLJS issues I worked on… I think you aren’t even building on Travis CI anymore? So can die too. Oh and seems to have dependencies on Windows issue, so feel free to kill it too.


Any ticket? would be great to fix IMO. Clearly a bunch of effort has gone in to data_literals.cljc already and hopefully not much more would be required to make it work