- 🛈 Background
- 🗲 Why I'm excited
- ✍ Current status
Lambda lists being one of the most omnipresent features in Common Lisp, obviously it would be incredibly useful to be able to manipulate them easily.
Very few projects even try to tackle this problem, and none of them make a good job of it or are enjoyable to use.
first-class-lambda-lists will provide a simple unified extensible way of processing lambda lists.
It will make it very easy to add support for new lambda list keywords and lambda list types.
A system for easily converting higher-level lambda lists to their lower-level equivalents is also planned.
The project is about 80% complete, but stalled and not yet usable. Life is hard! ¯\_(ツ)_/¯
As far as I'm concerned, metabang-bind has a good core concept, but takes the wrong design decisions at nearly every turn.
This is unfortunately stalled on, among other things, first-class-lambda-lists.
All existing web frameworks suck.
(No, I don't need to review them to know it's true.)
My second web framework will make it easy to manage hundreds of (heterogeneous) subdomains, and will feature full semantic tracing as a core feature.
I have several awesome ideas for this, which I mostly forgot because I haven't revisited this stuff in a while, but they are sure to come back when I finally get back to this...
I'm already a pretty advanced expert in Common Lisp, HTML5 and CSS3, and I'm building on the experience of my first fairly advanced web framework, so I have a very solid base to start.
I already single-handedly wrote and am successfully managing 100+ mobile-optimized HTML pages written in raw HTML5 and CSS3, spread across 25+ subdomains in 4 main websites, so clearly I am VERY motivated to finally make a great web framework, and it had better make it super easy to manage several dozens of subdomains because my web presence is only going to expand...
The CLHS cannot be updated and exhibits terrible usability on mobile. This is an extremely sad state of affairs for our most important resource.
I should clearly do this once my second web framework is up and running, because doing it by hand, although technically possible, would be just too insane.
I already know what this will be called, but I'm keeping the name under wraps until a first release.