4 ms·
I think churn in NPM might be an effect of how quickly the browsers and language are evolving. There’s always some new interface that will make your existing co
by Waterluvian 4y ago
I think churn in NPM might be an effect of how quickly the browsers and language are evolving. There’s always some new interface that will make your existing code faster or cleaner.
- dboreham 4y agoMy sense it is cultural. If there's no consequence for breaking stuff then stuff gets broken. Other languages have a stronger culture of shame from breaking stuff.
- interactivecode 4y agoThinking we need to shame our colleagues more is a really bad take. You can like your obscure programming language for all sorts of reasons, but if they go around shaming people I'm not surprised people would rather use a friendlier language.
- toast0 4y agoWell, what other way to influence behavior do we have? If a dependency update breaks my code, it reduces my opinion of that dependency. But if it's the least-worse option, and it's free, I can't do much other than think negative thoughts.
- kamma4434 4y agoSome, eg Clojure, have a culture of not breaking things. Having a library that remains unchanged for years is just fine.