←back to thread

The fate of "small" open source

(nolanlawson.com)
295 points todsacerdoti | 1 comments | 16 Nov 25 19:21 UTC | HN request time: 0.208s | source
Show context
p0w3n3d ◴[17 Nov 25 08:10 UTC] No.45951721[source]▶

  Given that some 80% of developers are now using AI in their regular work, blob-util is almost certainly the kind of thing that most developers would just happily have an LLM generate for them. Sure, you could use blob-util, but then you’d be taking on an extra dependency, with unknown performance, maintenance, and supply-chain risks.
Letting LLM write utility code is a sword that cuts both ways. You often create a throw-away code that is unproven and requires maintenance. It's not a guarantee that the blobutil or toString or whatever created by AI won't fail at some edge cases. That's why e.g. in Java there is Apache commons which is perceived as an industry standard nowadays.
replies(5): >>45952184 #>>45952590 #>>45953107 #>>45953418 #>>45958322 #
1. Menschlio ◴[17 Nov 25 11:11 UTC] No.45952590[source]▶
The proper way to do it, would be to have an industry standard on the default things people blindly but massivly pull through dependencies.

I also don't get how code can be so massivly inefficient. left-pad needs 9kb to download and the code is a handful of lines: https://www.npmjs.com/package/left-pad?activeTab=code

If my unit tests run through, i don't have 'unproven' code. I have well working code which doesn't need to go through a dependency hell upgrade cycle just because one function in that lib, i don't use, has some CVE too high to be ignored.