Re:The Lisp curse, now coming to your ecosystem
by gavinray on Thursday November 05, 2026 @12:22PM
(#50381740)
Great for static assets, potentially not-so-great for "load bearing" ;^) code
[ Parent
| on HN ]
Re:The Lisp curse, now coming to your ecosystem
by nonethewiser on Thursday November 05, 2026 @12:24PM
(#50381765)
Yes it does depend on the dependency, and a static asset is on one end of the extreme.
Re:The Lisp curse, now coming to your ecosystem
by andai on Thursday November 05, 2026 @12:25PM
(#50381783)
Every time I try to get a npm based project running (or one of my forks of one), half the packages don't exist anymore or I need to spend hours fixing breaking changes.
It's usually more straightforward to just rebuild it from scratch — not to mention infinitely more satisfying — and that was true before AI!
Re:The Lisp curse, now coming to your ecosystem
by gavinray on Thursday November 05, 2026 @12:28PM
(#50381831)
Language ecosystems tend to exist on a continuum. I love TypeScript but dread the dependency management because it's so often bit-rotted.
On the other hand, I routinely build Java/JVM projects with dependencies that haven't been updated in a decade that compile without issues.
Somewhere in the middle are most languages, I think.