News for hackers. Stuff that matters.
[dead]
Re:Clojure in the Age of Language Models by geokon on Friday October 09, 2026 @11:57PM (#50029401)
> the JVM isn't the only reason Clojure starts slowly, but it's still a major contributing factor

In case you didn't actually look at the links, but the evidence seems to point to this not being true (JVM startup is ~10% of the time)

> you're still hauling around a heavy runtime

> around 8 to 13 megs in size

I think if you jpackage a Clojure app with no GUIs or anything (that then bundles only the strictly necessary parts of the JVM) - it's around 50MBs. It's still embarrassingly slow to launch, involves ugly installers, doesn't provide crosscompilation and the memory usage makes Electron apps look lean.

That's to say, I think Jolt has a very valid place in all of this :) If I could plug in Clojure code and get out small fast executables for all major OSs (cosmopolitan?) that I can then share, that'd be useful for the rare situation I don't have any JVM dependencies

Re:Clojure in the Age of Language Models by yogthos on Saturday October 10, 2026 @12:17AM (#50029509)
I have yet to have a good experience with any JVM based app on the desktop with or without Clojure. Take a look at something like in IntelliJ as an example. It doesn't have a Clojure runtime, and it takes forever to start using gigs of memory. Like you said, it makes Electron apps look lean. I ended up switching to using VSCode because it just runs a lot better and uses less memory. And when it comes to Clojure specifically, ultimately it doesn't really matter whether the slowdown is JVM or Clojure specific. This problem has existed for around a decade now, I'm not expecting that it'll be addressed in the foreseeable future.

And yeah, Jolt solved this problem for me completely. Startup is fast, you get a single binary, and it runs anywhere Chez Scheme runs which is mac, Linux, Windows, Android, and iOS. The best part is that you can use FFI to access native ecosystem as easily as Python.

There's also some fun Burin's been working on porting OpenLdk to Jolt https://github.com/jlt-commons/jolt-openldk

It might make it possible to translate Java bytecode to Jolt, and then link it into the binary similarly to native libs as a statically linked fasl. That way there might not even be much of a runtime cost.

Re:Clojure in the Age of Language Models by geokon on Saturday October 10, 2026 @01:31AM (#50029891)
very cool!

and yeah, I dunno what's with Java apps being clunkers haha. I've come across games in Java that didn't feel bloated, but for some reason desktop apps almost always have a certain bloated feeling to them. Though I feel the same with Electron/VSCode (the input delay to me is very noticeable)

thank you for the work you do :)

Re:Clojure in the Age of Language Models by yogthos on Saturday October 10, 2026 @08:23AM (#50032208)
It's actually fun to read the code for Java games, people tend to do all the allocation up front to avoid GC pauses. So, it's a very unique style. :)

Very much agree on Electron, there is a noticeable lag, and it's always bothered me that making a native app has become such a chore that people now just package a browser to render the UI.

And thanks, it's always nice to hear that it is useful and appreciated. :)