Re:The Lisp curse, now coming to your ecosystem
by xscott on Thursday November 05, 2026 @03:34PM
(#50384125)
You could have a new web server and database too. Maybe a new one every other day so you aren't a stationary target.
[ Parent
| on HN ]
Re:The Lisp curse, now coming to your ecosystem
by kragen on Thursday November 05, 2026 @04:16PM
(#50384564)
I suspect that a more effective mitigation would be to have an LLM read all your HTTP requests and the actions the web server proposes to take in response and give a Jev-like approve/disapprove decision.
Re:The Lisp curse, now coming to your ecosystem
by xscott on Thursday November 05, 2026 @04:49PM
(#50384948)
All good, but I suspect we're thinking about different aspects. If I understand correctly, you're pointing out that nobody is tied to legacy software any more - they can spend 37 minutes to re-implement from scratch in a safe(r) language.
My point is that everyone doing their own thing their own way means an attacker doesn't get the next thousand sites for free after finding a vulnerability in one site.
Having an LLM as sentry is a fun idea too.
Re:The Lisp curse, now coming to your ecosystem
by kragen on Thursday November 05, 2026 @05:03PM
(#50385112)
Right, I agree.
Re:The Lisp curse, now coming to your ecosystem
by fc417fc802 on Thursday November 05, 2026 @07:32PM
(#50386606)
I assume that was sarcastic but I think it would actually work fairly well? At least if the ends could justify paying for that many tokens.