3 ms·
I don't understand how you can say that versioning isn't a hard problem when you've been developing for a long time. Every major release brings a host of change
by jbob2000 9y ago
I don't understand how you can say that versioning isn't a hard problem when you've been developing for a long time. Every major release brings a host of changes, and every release, you have to litter your codebase with "if version > x do this else do this". There is utter chaos for the first few days while the development community not only orients around the OS changes, but also how every phone manufacturer has bungled the changes (Samsung, being the worst at this).
- EddieRingle 9y ago> Every major release brings a host of changes, and every release, you have to litter your codebase with "if version > x do this else do this". I rarely, if ever, have needed to do this, and I've been working with Android since 2009. Most of the time that is abstracted away by the support libraries, anyway. The version fragmentation generally isn't a huge issue for Android app developers, in practice.
- on_and_off 9y agoSame thing here. Yeah there are some `if (SDK_INT > x)` but I can't really say that the code is littered by those. I can spend weeks (maybe months) without having to make such a check. We also have some OEMs specifc bugs that need addressing from time to time. Again, this is very annoying but not a 'significant' part of the effort.