3 ms·
If you define the "modernization" as mindlessly switching to a trending framework or library, the cost is inevitable even without package managers.
by lifthrasiir 7y ago
If you define the "modernization" as mindlessly switching to a trending framework or library, the cost is inevitable even without package managers.
- squiggleblaz 7y agoYou don't need to mindlessly switch to a trending framework or library. Try upgrading typescript to the latest version. I think that's a fair definition of "modernisation" and something which should be benign. But now all of a sudden you have to upgrade every dependency to the latest version - or write your own .d.ts files - since they're typically written to the current library version - typescript version combination.
- gpm 7y agoThe rust eco system has done a pretty good job at this. The language and standard library is always backwards compatible (minor security fixes excepted). So updating to a newer language version just works. Major libraries at the roots of many dependency trees have upgraded in backwards incompatible ways a few times, but the community has pretty consistently come together and helped move every other library that anyone uses to the new version.
- choeger 7y agoI define modernization as anything from updating frameworks, over libraries, tools, to the language itself.