675 karma · joined May 2, 2017
All hardware was owned by various organizations acting as "sponsors". But at this point most of it might have been replaced by servers owned by Lee.
One of the sponsors, whose server hosted freenode's email server, pulled out shortly after the volunteers left.
Libera.Chat does have a non-profit, however, according to the announcement.
Edit: oh and it has already taken off as much as it will, the ZigBee alliance is working on a an ipv6 based standard.
It could also choose to invoke a restart. Restarts are basically code to handle a problem, but they don't catch any conditions. Instead, they can be invoked, usually from a condition handler. So you would have an error being signaled at the lowest level of your code, various recovery strategies defined at appropriate intermediate levels of code, and at the highest level of code you could have a condition handler defined which picks whichever restart is best for the high level situation. So a library author can provide many different restarts, signal errors very deep in the library, and then let the library user choose the recovery strategy that fits their requirements.
If no matching handler is found, typically the debugger would be invoked, and when running with a suitable IDE like Emacs with Slime or Sly, a window with a stack trace will pop up. Here, if there were any available, restarts can be invoked directly by the programmer while they are debugging
Finally, the condition system can be used to signal non-erroneous conditions, that can optionally be handled.
I do this with threads but my system is just a chat bot, so it doesn't really ever turn into a problem.
I wouldn't consider something a dialect unless they were similar enough that most code that works in one works in the other with minimal modification. Old Lisp code does not work in Scheme. A lot of it does however work in Emacs Lisp and Common Lisp.
So Scheme being in a Lisp "family"? Sure. But not a dialect.
I have a Discord bot written in CL. If I want to add a new command or feature, I write it, hit a few buttons, and it seamlessly integrates with my bot without interrupting anything it's doing.
If I have a problem with a macro, I can hit a button to have it expand right there in my code, and when I see the problem I hit a button to unexpand it.
The editor will even catch errors and ask what you want to do, without interfering with other threads, which has been very useful while developing my bot.