April 22, 2026
Come for CSS, stay for license wars
Olive CSS: Lisp powered vanilla CSS utility-Class A la Tailwind
New Tailwind-style CSS in Lisp drops — and the license fight steals the show
TLDR: Olive CSS is a Tailwind-style utility CSS framework written in Lisp and released under an LGPL license, with heavy customization options. The lone standout comment sparked a fresh copyleft‑vs‑permissive debate after a page labeled MIT as not “free,” turning a code drop into a freedom‑of‑software food fight
Olive CSS just rolled in: a Tailwind-style utility class library powered by the Lisp language (Guile Scheme), promising plug‑and‑play classes, lots of customization, and a "hack everything" vibe. It’s free software under the LGPL license, and the docs are up, including the API. But the feature list wasn’t what lit up the comments — the license did.
One early commenter laser‑targeted a comparison note that called the MIT license not “free” because it’s not copyleft. Cue the classic copyleft vs permissive showdown: is “freedom” about protecting downstream freedom (copyleft), or maximum do‑what‑you‑want flexibility (MIT)? The single pointed question — “How can more permissive be less free?” — was enough to reignite the age‑old flame war. Drama level: high.
Meanwhile, the project’s own philosophy leans hard into hackability and learning, with warnings that the default CSS file is hefty unless you trim features, colors, breakpoints, and dark mode. Fans of tweak‑everything config will love the knobs; others are already side‑eyeing the “big by default” note. But today’s headline isn’t the code — it’s the definition of freedom. Olive CSS wanted to be a Tailwind‑style alternative written in Lisp; the internet wanted to argue what “free” means. Choose your fighter: ideology or utility. Either way, you’re getting a front‑row seat to the license wars
Key Points
- •Olive CSS is a Tailwind-inspired utility-class CSS framework written in Guile Scheme and usable in any web project.
- •The project’s source code is licensed under LGPLv3+; its documentation and examples are licensed under FDL 1.3+.
- •Installation involves downloading a pre-built CSS or building your own and including it via an HTML <link> tag.
- •The default build is large; production use is advised to create a custom build by disabling unused colors, breakpoints (e.g., xl/2xl), and dark mode.
- •Customization is enabled via Scheme (parameterize, addmq, addhover), allowing control over features, breakpoints, color palettes, and variants; server-side caching and GZIP/Brotli compression are recommended.