4 ms·
Because with big enough project you have 2 ways: You update dependencies as a full time job and it bites you because something breaks big way. But most likely
by ozim 3y ago
Because with big enough project you have 2 ways:
You update dependencies as a full time job and it bites you because something breaks big way. But most likely you have some help to fix it and as you are on top you might need to put work to fix it but yeah still full time job.
You neglect updating dependencies and it bites you and you don’t even expect it just because you have to update something you did not expect will need it and you are now scrambling to do anything because you are messed up.
Besides I like writing my own code more than dealing with some lib shenanigans.
- dspillett 3y agoOr you neglect updating them and get bitten by a missed security update, either just the rush to update (and potentially deal with breaking changes and other issues that come from not having done so in a long while) worse because it actually affects your projects instances in the wild.