zlacker

I've always been troubled with the "observability" of Erlang/otp, because everytime I had to fire up wobseever, it was because I had put my system in such an unresponsive state (infinite message loop, some single actor congestionned because of third party code, or a supervisor tree crash looping because of a typo in the name of a variable that no compiler was there to catch) that wobserver _itself_ was useless.

And for the "sequential" part of the program, I would have loved a debugger on par with what's in my browser's dev tool, but it goes against the Erlang philosophy, or something.

Still, I can't wait to try smalltalk when it becomes relevant again thirty years in the past ; and if it's strangeloop video season _again_, and since I still can't write native clojure, I guess I'll try to install sbcl _again_ and set up slime _again_ and see if I get it, this time ?

>>phtriv+(OP)
You may want to try Sly rather than Slime, you may prefer its UX.

Speaking of SBCL and Clojure, I have used Stumpwm and the Nyxt browser for a while and they both seem to run very well; I wonder if CLJ has any nice desktop applications that show off how it runs.

>>tmtvl+Uf
You're right, apparently the default slime-like mode is sly, I suppose that's what all the uncool kids use nowadays ;)

To be fair, clojure was designed with long lived servers in mind, so the "JVM takes ages to start and load the class path" tradeoff makes sense. A downside is that any GUI built in clojure will either has to jump through some AOT compilation hoops (graalvm, etc), or accept being slow as hell to boot.

This alone has been enough to dissuade me to write anything with a UI in clojure. Maybe the space has changed since last time I tried, though.