Every function is unsafe.
No references, only pointers.
No cargo, build with rustc directly.
No std, but libc is allowed.
Only Edition 2021.
All user structs and enums #[derive(Clone, Copy)].
Everything is pub by default."
Damn if only they told us yesterday before I restarted for the first time in a month. I wonder how big my memory leak would have been. I have only been online for about 11 hours (~9 of those were in hibernation) now and already at a 13MB leak.
I reported that to them and at least based on the interaction they have no idea for last few months. I just have to restart them or the whole MacBook Air from time to time. I suspect it is not their issue lately as I saw others have this issues. Well … now I know. Or may be I just guess.
I've never read a book from MWL that wasn't entertaining and full of knowledge even in a field where I had years of experience.
Big Tech tought us that Running Your Own Mail Server is too hard, too complicated and coerce sysadmins by flagging mail from independent mail servers as Spam.
I'm looking forward to this book and hope that MWL will address that particular problem in detail.
There is also now a very good Common Lisp plugin for Jetbrains IntelliJ which was just released a few days ago.
On the other side, as a developer, you should not be dependent on a single web-based editor to use a specific language. There are many great programming languages out there that run best _outside_ VSCode and I'm glad they still exist.
If you overlook the power of Lisp (and all the effort that is going on in Common Lisp, Racket, Scheme communities etc.) than this is really your loss.
Amazing work by the author of the Common Lisp Cookbook.
I've hesitated to get into CL for months, but seeing about all the activity going on, I'm in for 2023.