3 ms·
All the teams will need to migrate sooner or later so figuring out all of the potential problems in migrating and having everyone do it an once is more efficien
by charcircuit 4y ago
All the teams will need to migrate sooner or later so figuring out all of the potential problems in migrating and having everyone do it an once is more efficient than each team needing to figure it out separately.
- mjr00 4y agoThat's not how it plays out in reality. usually nothing gets done because "upgrade this package" is never on anyone's priority list. Or teams end up doing shit like JAR shading or forking and renaming a package with some _v2 or whatever suffix to be able to support both the old and new version simultaneously in the main code base. And then of course nobody ever updates the runtime (hello, enterprise monoliths still running on Java 6/7!) It ends up being a complete mess.
- NBJack 4y agoI'm just grateful a language like Java has any sort of namespace solution to dependency nightmares. I have lost track of how many times I did a git pull on a Python based solution only to find I broke all the things when I tried to upgrade one package.