caveman
doc
Our great sponsors
caveman | doc | |
---|---|---|
10 | 8 | |
757 | 15 | |
- | - | |
0.0 | 7.0 | |
over 1 year ago | 19 days ago | |
Common Lisp | Common Lisp | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
caveman
- How do you think about version number management?
- I want to pursue this web app project - advice using CL?
-
Mito: An ORM for Common Lisp
We are going to walk through the examples by building an online Warehouse management system using Caveman
-
Using SVGs in Common Lisp web apps with Djula
Djula is a port of Python's Django template engine to Common Lisp. It's the default templating engine used by the framework Caveman for building web applications
-
Is Woo still "beta quality" or prod ready?
Appreciate it. Can I ask one last thing. Between Snooze and Caveman2, which is the more current project?
-
Practical? Common Lisp on the JVM: A quick intro to ABCL for modern web apps
This is interesting from a "look what we can do!" perspective, but practically speaking, I'm not sure there's a good reason for doing it this way. For all practical purposes, it would be better to use one of the "native" Common Lisp libraries for doing this, such as Caveman: http://8arrow.org/caveman/
Even as a big Common Lisp fan, I would really question using it in a situation where the project has strict requirements to use a particular framework for another language.
-
Building Common Lisp web apps with Tailwind CSS
In this post, I am going to walk you through to setup Tailwind CSS for a Common Lisp web application using Caveman. If you want to know more about creating web applications using Common Lisp and Caveman, please check my previous posts on the topic.
-
Building a Rentals Listing web application in Common Lisp
We are going to use Caveman for scaffolding this project. Caveman is a lightweight web application framework created by Eitaro Fukamachi for Common lisp. Caveman is available on Quicklisp, so you can install it with:
-
Lisp for the Web - 5
Hence I chose Caveman for this project. After having been played around with and without Caveman for building web applications in Common Lisp, I found that it is the best framework out there for developing web apps in Lisp. Caveman is a lightweight web application framework created by Eitaro Fukamachi for Common lisp. Fukamachi has got some serious tools for doing web development in Lisp. Please feel free to check out his Github profile for more useful tools.
-
How to deploy Caveman applications to Heroku?
I have been trying to come up with a standard template using Caveman to deploy on Heroku. But I am struck with these issues, not quite getting it to work with the available buildpacks. Lot of the related articles are hopelessly outdated. Appreciate any help or pointers? https://github.com/fukamachi/caveman/issues/126 https://gitlab.com/duncan-bayne/heroku-buildpack-common-lisp/-/issues/6
doc
-
How do you think about version number management?
- it is possible to subscribe on the changes using RSS (this is a feature of the 40ANTS-DOC documentation builder).
-
From Common Lisp to Julia
So, the article is harsh on CL: YMMV. Also, your goal may vary: I want to build and ship (web) applications, and so far Julia doesn't look attractive to me (at all). Super fast incremental development, build a standalone binary and deploy on my VPS or ship an Electron window? done. Problem(s) solved, let's focus on my app please.
The author doesn't mention a few helpful things:
- editor support: https://lispcookbook.github.io/cl-cookbook/editor-support.ht... Emacs is first class, Portacle is an Emacs easy to install (3 clicks), Vim, Atom support is (was?) very good, Sublime Text seems good (it has an interactive debugger with stack frame inspection), VSCode sees good work underway, the Alive extension is new, usable but hard to install yet, LispWorks is proprietary and is more like Smalltalk, with many graphical windows to inspect your running application, Geany has simple and experimental support, Eclipse has basic support, Lem is a general purpose editor written in CL, it is Emacs-like and poorely documented :( we have Jupyter notebooks and simpler terminal-based interactive REPLs: cl-repl is like ipython.
So, one could complain five years ago easily about the lack of editor support, know your complaint should be more evolved than a Emacs/Vim dichotomy.
- package managers: Quicklisp is great, very slick and the ecosystem is very stable. When/if you encounter its limitations, you can use: Ultralisp, a Quicklisp distribution that ships every 5 minutes (but it doesn't check that all packages load correctly together), Qlot is used for project-local dependencies, where you pin each one precisely, CLPM is a new package manager that fixes some (all?) Quicklisp limitations
> [unicode, threading, GCā¦] All of these features are left to be implemented by third-party libraries
this leads to think that no implementation implements unicode or threading support O_o
> most of the language proper is not generic
mention generic-cl? https://github.com/alex-gutev/generic-cl/ (tried quickly, not intensively)
Documentation: fair points, but improving etc. Example of a new doc generator: https://40ants.com/doc/
Also I'd welcome a discussion about Coalton (Haskell-like type system on top of CL).
-
Kons-9 update ā 3D Common Lisp system now on MacOS and Linux
Great news! Feedback: I guess it's time to start working on documentation ;) The readme doesn't say what the system does. I guess you could maintain a high overview "manually", and in parallel set up a documentation system (40ants doc is kinda cool). Best,
-
Favorite Lisp project? Shameless plugs welcome & encouraged!
- and 40ANTS-DOC builder.
-
Why Turtl Switched from Common Lisp to JavaScript
That is why I've put about half of this year into the Common Lisp documentation generator for all of my libraries.
If you are interested, please read it's docs and join the effort of making good documentation for CL projects: https://40ants.com/doc/
-
CL-TAR Project
And the doc is built with the new https://40ants.com/doc š Really cool.
- Does everyone here manually specify the entire project's dependency tree in .asd files?
What are some alternatives?
lisp-for-the-web - Code for lisp for the web post
wookie - Asynchronous HTTP server in common lisp
slime - The Superior Lisp Interaction Mode for Emacs
woo - A fast non-blocking HTTP server on top of libev
cl-super-rentals - Super rentals in Common Lisp
cl-lsp - An implementation of the Language Server Protocol for Common Lisp
heroku-buildpack-common-lisp
weblocks - This fork was created to experiment with some refactorings. They are collected in branch "reblocks".
clack - Web server abstraction layer for Common Lisp
cl-permutation - Permutations and permutation groups in Common Lisp.
easy-routes - Yet another routes handling utility on top of Hunchentoot
LispSyntax.jl - lisp-like syntax in julia