|
|
|
|
|
by nme01
1196 days ago
|
|
Isn’t the proposal simply saying that making libs more granular will solve the problem? I don’t know what’s everyone else’s experience but I was updating dependencies due to either bugs identified in old versions, because I wanted a new feature or because the old version was not supported anymore. Setting dependency to a fixed version was not an option. Using in your code function with given version fixed seems to be problematic. During updates the problem was to update all other dependencies as a result of the update. I can’t see how the proposed approach would solve it. Another problem which I sometimes faced (less annoying) was the api change i.e. start using function B instead of function A which requires slightly different parameters. Those kind of automatic refactors could be supplied with library upgrades (some libs already come with automatic migration “scripts”) |
|