5 ms·

That's a great idea! Let's try and deploy this 'left-pad' function that everyone can use... But seriously, I know his description is a bit different, but I thi

That's a great idea! Let's try and deploy this 'left-pad' function that everyone can use... But seriously, I know his description is a bit different, but I think NPM has shown that such a model is really difficult to maintain.

tosh 7y ago
Functions in a global persistent database would solve the "dependency suddenly disappearing" problem.
- jakear 7y ago
  “Global persistence” is a lie. The second copyright law or malware become involved, practice separates from theory. Look at the hackage rollback, for instance. (https://hackage.haskell.org/package/Facebook-Password-Hacker-Online-Latest-Version-1.0.1 https://hackage.haskell.org/package/Facebook-Password-Hacker... <- downloads what used to be a Hackage package to your computer. Now, its a text file with the word "Gone")
  - tosh 7y ago
    bittorrent, blockchains
- christophilus 7y ago
  I don't think it's just the persistence that's the problem. NPM is now persistent (I think). But it's the fact that you can upgrade the functions. So, maybe if the references were immutable, it'd make more sense. But then it's the fact that you've got a bunch of one-off functions which are a security nightmare to audit, not to mention accidentally slurping in several MB of functions due to the dependency graph.