3 ms·
I think that the reason NPM responded this way is because it was a premature optimization. If/when NPM has a problem - storage costs are too high, or transfer
by efitz 2y ago
I think that the reason NPM responded this way is because it was a premature optimization.
If/when NPM has a problem - storage costs are too high, or transfer costs are too high, or user feedback indicates that users are unhappy with transfer sizes - then they will be ready to listen to this kind of proposal.
I think their response was completely rational, especially given a potentially huge impact on compute costs and/or publication latency.
- deleted 2y ago[deleted]
- maccard 2y agoI disagree with it being a premature optimisation. Treating everything that you haven’t already identified personally as a problem as a premature optimisation is cargo cutting in its own way. The attitude of not caring is why npm and various tools are so slow. That said, I think NPM’s response was totally correct - explain the problem and the tradeoffs. And OP decided the tradeoffs weren’t worth it, which is totally fair.