6 ms·
FWIW I regularly (every month-ish) update all my dependencies in my native iOS projects (cocoapods) and it’s exceedingly rare that things break and when they do
by kitsunesoba 8y ago
FWIW I regularly (every month-ish) update all my dependencies in my native iOS projects (cocoapods) and it’s exceedingly rare that things break and when they do, it’s a matter of tweaking <15 lines of application code to fix. Stuff really only gets ugly if you go upwards of a year without updates, and even then it’s still somewhat manageable.
So maybe some library ecosystems are worse than others.
- Benjammer 8y agoI've had the same experience with the current enterprise Android project I've developed and maintained by myself (at a company). I have my library versions all in my top level gradle file and every few cycles I'll go through and update everything to latest and just build the app and see what happens. It's rare anything bad happens at all. I encounter far more trouble upgrading gradle and the build plugin itself than my dependencies.
- vorg 8y ago> I encounter far more trouble upgrading gradle and the build plugin itself Could be time to switch from Gradle to Bazel. It would also be nice to see the last of Apache Groovy, don't you think?