I've worked on PAIP, and I think the GitHub.com version - https://github.com/norvig/paip-lisp/ - gets more attention than the GitHub.io version linked here. The GitHub.io version automatically gets updates, I think, but I'm not verifying the Markdown works over there.
Having the data structures is nice and all, but using them is kind of painful. They are certainly second class.
Having to use accessor functions or destructuring macros instead of just a period or -> is often annoying too. The lack of syntax has cons as well as pros.
As someone who's dabbled with Scheme, Clojure, and CL long ago and started wanting to get back into CL, I really enjoyed that course as a combination refresher plus deep dive into some topics I didn't really know before (including CLOS).
My main takeaway was multi-methods, they didn't really click for me before I started seriously digging into CLOS. I wish more languages supported them/played around with similar ideas.
What do you expect from a web framework? That means different things to different people. I don't really like frameworks, so I used a web-server abstraction layer named "clack."
Radiance[0] is a more traditional web-framework, with interfaces for backend-storage, web-servers, templating, authentication &c.
Hunchentoot gives you basic route definitions out-of-the-box (bring your own database), and for something more full-featured there is CLOG[1] and Reblocks[2]
Might be worth checking out this[1], one of the sites linked from awesome-cl that teaches setting up webdev. And looks like it uses Hunchentoot which is what I've always seen every time I looked into backend webdev in CL
I really like this, as from an outsider it seems that CL doesn't have a community and the few packages it has are more like building blocks for customizing and implementing you required functionality rather than packaged black boxes. With all those new languages, it appears that the value proposition of CL is dwindling, static checking feels primitive, macros are easily attainable now, and live runtime image manipulation misses the point on the world of short lived containers.
CL has Coalton, which is the implementation of a static type system beyond Haskell 95. Full multiparameter type classes, functional dependencies, some persistent data structures, type-oriented optimization (including specialization and monomorphization). All integrated and native to CL without external tools.
Live image manipulation isn't quite as useful as it once was for runtime program deployment. But it's still a differentiating feature for incremental and interactive development—before you compile binaries to deploy. Tools like Jupyter notebooks don't come close for actual (especially professional) software development.
reply