Hacker News Reader

Comment by swiftcoder | Hacker News Reader

> Programmers are rewriting and reinventing the same techniques more often than any other vocation I can think of

And the answer to that is clearly a tool that makes rewriting/reinventing cheaper than actually packaging nice reusable libraries

View on HN

Nice reusable libraries are still a core part of most AI projects, but honestly I think it's not a terrible approach with all the updating dependency malware issues with stuff like NPM.

> I think it's not a terrible approach with all the updating dependency malware issues with stuff like NPM

I think in this instance, the only thing worse than a zero day in your dependency tree, is a zero day you don't know your LLM vendored directly into your codebase...

Personally I feel a vulnerability in local code (unshared ai slop) is much less likely to be exploited, than for say a npm package update that will pwn you as soon as it loads up.

And on other hand I really do not understand how basic project boilerplate templating wasn't already a fully solved issue. Surely it should have been doable...

I guess the nice thing about AI is it points to the things that we really need to figure out how to abstract instead of rewriting from scratch all the time.

I'm all for packaging nice reusable libraries, but someone has to actually do it. A lot of them just don't exist (yet).

I sort of hold the opposite view: pretty much anything I want to do, there are about ten competing libraries/frameworks/languages, and the lack of commonality across them means I'm often wedged into weird ecosystem choices

Reply on news.ycombinator.com