Shinmera

My own experience is usually more that there's 0.

Common Lisp is not a batch compiled language, it relies on having a running program in order to compile your code. As such you must be running on the target platform to deploy for to produce executables.

I've developed most of my libraries for windows on linux and used wine for testing and development, only using a VM for final confirmation.

Unfortunately Darling still can't even run SBCL.

Thanks! :)

Not sure when that was introduced into SBCL, but suffice to say your version is too old.

If you're on Linux or Windows you can try it out yourself with SBCL:

(ql-dist:install-dist "http://dist.shirakumo.org/shirakumo.txt")
(ql:quickload :trial-examples)
(trial-examples:launch :scene-loader)

It does if you donate to my patreon so I can keep making cool stuff in it: https://patreon.com/shinmera

For a different answer, a tool like a programming language has a future as long as people keep finding it useful. If that very pragmatic answer isn't enough and you have more esoteric ideas of what a future is, such as it needing to be capitalistically viable, then you're driving a harder bargain. There's still a future in that, too, though. Even without specific companies using it, there's plenty of opportunities as a consultant to implement solutions using lisp. And if a future to you means it needs to be mainstream popular, then you're going to have to somehow come into the possession of millions of dollars to fund and lobby various companies and educational systems to use it.

Personally I'm not really sure what this humm-hawwing really solves. Just make cool stuff and enjoy your time?

Define lisp first.

All that happens when you recompile a function is that a new function object gets created, and the name of the function is updated to point to that new function object.

But the old function is still the one actually running. For your new function to be used, it has to be called, first. What you can usually do then, is to create a secondary function, step, or whatever you want to call it, and have that be called in the main loop. Then, because step will exit and be re-called every update, when you recompile it, the new step will be executed, too.

Heya, just wanted to say thanks for using my new name despite the old one still being on the paper you linked! ❤️