Depends on how hard you want to stretch the definition of "Lisp" here. But I guess if someone would make a proper Lisp for CLR and marry Emacs with PowerShell, then we'd be half-way towards resurrecting the corpse of Lisp Machine into a functioning zombie.
How is Nyxt? I've been meaning to try it out. Is it usable for day-to-day tasks? What are the remaining 30% of your use?
As for Guix, I've approached it twice, both times installing (what was then known as) GuixSD. Couldn't really make it work. What are your experiences? And your configuration? :).
Emacs, that I swear by.
Still, what's missing in this picture, and why I mentioned PowerShell, is a typed integration with entire OS. Operating on objects / typed data, invoking functions - instead of passing unstructured blobs of text around. That's what I like about PowerShell approach - my scripts don't invoke CLI utilities, they ask system for objects, inspect them, call into their methods. This is similar to the Lisp Machines, where you could code against objects representing your OS runtime state.
If we could somehow bolt that on top - replace existing Unix tools with ones accepting and producing structured data (or even wrap them) - then the picture would be complete. And I wouldn't mind using four different Lisps, if that's what it takes :).
The last 30% of internet usage is work related stuff (checking email, issues for our internal git, time entry, etc. stuff that’s only available to “approved” browsers).
To make guix system work I had to compile my own proprietary kernel and build an installation image for it. Afterwards I’ve only had minor software and driver issues. I even have steam running now.
So I hear you and through stumpwm I guess I get to work with structured data for window management. It isn’t typed but windows are represented as objects to be manipulated. Thanks to the repl I can change window behavior on the fly and have it reflected immediately.
Guix provides structured ways of manipulating system services and configurations. Most of that stuff has an interface with scheme records.
For instance my sddm configuration is a scheme record that gets tangled (for lack of a better word) into a text file.
With guix one can also use g-expressions to write configurations or execute programs in a monad of some sort.
It isn’t typed but the setup is far from unstructured.
I'm still confused about the state of Clojure CLR. I initially thought it was the "OG Clojure" before Rich dumped CLR and went for JVM instead. Is it maintained properly and kept up to date with Clojure proper?
(I used to be in the "Clojure is not Lisp" camp, but I've grown up at some point.)
My understanding is that the Clojure community points everyone to Arcadia[0] since it's maintained and a bit more public about what their exact goals are. Unfortunately, neither are terribly well documented and so I've not personally used either
I just tried it out of curiosity and the startup time is absolutely brutal:
-▶ time dotnet ./Clojure.Main.dll <<<""
Clojure 1.10.0-beta1
user=> user=>
dotnet ./Clojure.Main.dll <<< "" 16.74s user 0.18s system 99% cpu 16.980 total
Compared to Clojure on JVM:
-▶ time clojure -e '(System/exit 0)'
clojure -e '(System/exit 0)' 3.02s user 0.16s system 268% cpu 1.184 total
I wonder, did I do something wrong (I'm not a .NET developer by any stretch) or does it simply take that much time on the CLR?
.NET may suffer from the same problem as Julia: the first runs will trigger the jit system and result in awful start times. There are ways to avoid this, but I don't know if it works (yet) for clojure.
