YHacker Newsscreenshots

Screenshot of javahippie.net: The Lisp curse, now coming to your ecosystem

First screen, captured 8 days ago. Open the video.

The Lisp curse, now coming to your ecosystem

More from javahippie.net →

Blog post arguing that LLM code generation may bring the 'Lisp curse' to ecosystems like Java, reducing library reuse and open source collaboration.

What HN thinks

Everyone is now a Lisp hacker, whether they wanted the curse or not.

Reimplementing beats dependencies now
With LLMs making custom code cheap, many argue fewer dependencies means less supply-chain risk, less bit-rot, and code that fits exactly; some even see vulnerability diversity as a plus.
Some libraries must not be rewritten
Others counter that crypto, numerics and battle-tested code can't be matched by homemade versions, and vendoring raises license and unpatched-vulnerability problems.
The Lisp curse is overstated
Lisp users say the CL ecosystem is healthy with ubiquitous libraries like ASDF and UIOP, and the 'curse' is a myth or applies to all languages.

Consensus: No firm consensus, though most agree LLMs shift the tradeoff toward writing more code yourself, with security-critical areas still best left to mature libraries.

Recommended in the comments

libgit2 (library): Cited as a case where integrating a mature library beats reinventing it.
Lem (tool): Pointed to as a lively project in the Common Lisp ecosystem.
ASDF (tool): Named as a ubiquitous, readable Lisp library that disproves the curse.
Closer MOP (library): Listed among widely reused, de facto standard Lisp libraries.

Summarised by Claude from the comment thread 8 days ago.

Points: 211
Comments: 166
Best rank: #4
Posted: 2026-11-03 by marcolinux
Category: Programming

llm-assisted-coding lisp-curse open-source java software-ecosystems libraries

All captures:

Full page

Full-page screenshot of javahippie.net

Captured 8 days ago. Click for the whole screenshot.

Looks similar

Screenshot of emptysqua.re: Intro to TLA+ for the LLM Era: Prompt Your Way to Victory

Intro to TLA+ for the LLM Era: Prompt Your Way to Victory (emptysqua.re)

126 points by zdw 6 months ago | 27 comments

Screenshot of journal.paoloamoroso.com: Exploring Interlisp-10 and Twenex

Exploring Interlisp-10 and Twenex (journal.paoloamoroso.com)

16 points by naves 1 year ago | 0 comments

Screenshot of chrisgregori.dev: Code is cheap now, but software isn't

Code is cheap now, but software isn't (chrisgregori.dev)

83 points by fs_software 10 months ago | 33 comments

Screenshot of lewiscampbell.tech: The insecure evangelism of LLM maximalists

The insecure evangelism of LLM maximalists (lewiscampbell.tech)

189 points by todsacerdoti 10 months ago | 174 comments

Screenshot of blog.lyc8503.net: Building my own network stack

Building my own network stack (blog.lyc8503.net)

91 points by uneven9434 2 months ago | 74 comments

Screenshot of evanhahn.com: Local LLMs versus offline Wikipedia

Local LLMs versus offline Wikipedia (evanhahn.com)

288 points by EvanHahn 1 year ago | 171 comments

Related stories

Screenshot of vivienhenz.com: Why Common Lisp is now the best programming language

Why Common Lisp is now the best programming language (vivienhenz.com)

242 points by misterchocolat 1 month ago | 306 comments

Blog post arguing Common Lisp is the best programming language now that LLMs write code, because its image-based, interactive model shortens the feedback loop.

common-lisp lisp llm-coding repl

Screenshot of opensourcesecurity.io: Open Source is one person

Open Source is one person (opensourcesecurity.io)

325 points by LawnGnome 1 year ago | 132 comments

Blog post by Josh Bressers on Open Source Security arguing that many open source projects are maintained by a single person.

open-source-maintainers software-supply-chain open-source-sustainability josh-bressers

Screenshot of blog.djhaskin.com: Why I Chose Common Lisp

Why I Chose Common Lisp (blog.djhaskin.com)

328 points by djha-skin 1 year ago | 145 comments

Blog post explaining why the author left Clojure after seven years over slow startup times and chose Common Lisp as their hobby language.

common-lisp clojure lisp graalvm-native-image

Screenshot of taalas.com: The path to ubiquitous AI (17k tokens/sec)

The path to ubiquitous AI (17k tokens/sec)(taalas.com)

804 points by sidnarsipur 8 months ago | 436 comments

Taalas blog post by Ljubisa Bajic arguing that latency and cost limit AI adoption and presenting its approach to very fast (17k tokens/sec) inference hardware.

ai-inference ai-chips llm-latency taalas

Screenshot of bitlog.com: Software may be getting worse, but it used to be horrible

Software may be getting worse, but it used to be horrible (bitlog.com)

282 points by jakevoytko 17 days ago | 309 comments

Blog post by Jake Voytko arguing that while software may be degrading today, software from the 1990s and 2000s was far buggier, citing crashes, lost work, and insecurity.

software-quality windows blue-screen-of-death retro-computing

Screenshot of philschmid.de: The new skill in AI is not prompting, it's context engineering

The new skill in AI is not prompting, it's context engineering (philschmid.de)

832 points by robotswantdata 1 year ago | 467 comments

Blog post by Philipp Schmid arguing that context engineering, supplying LLMs with the right information and tools, matters more than prompting for AI agents.

context-engineering prompt-engineering ai-agents llm