4 ms·
> Annoyance the 5.1beta3 – Version incompatibility That makes no sense. Yes, version X+1 is incompatible with version X. That's why we upped the version number
by njharman 11y ago
> Annoyance the 5.1beta3 – Version incompatibility
That makes no sense. Yes, version X+1 is incompatible with version X. That's why we upped the version number!!!
I wonder if author never had to deal with API/Service that changed and was poorly or unversioned. Suddenly and mysteriously breaking things.
- ktRolster 11y agoIt's annoying when an API isn't backwards compatible for no good reason. Android increases their version numbers quite often, which means you have to do extra work (which is annoying if someone is paying you, but worse if someone isn't). Crockford said, "Changing an API is an act of violence." An API designer should think long and hard before breaking backwards compatibility: usually it's not necessary.
- izacus 11y agoUh... Android's APIs are one of the most backwards compatible I've worked with (most applications written for 2.0 will work without issues on new Androids). Could you elaborate what extra work do you have to do? In comparison to what?
- noselasd 11y agoHe's saying that APIs not providing backwards compatibility is annoying. So yes, it's annoying when the next android release is out just as you're finishing your app, your code no longer works and you'll have to rewrite parts just because, while not receiving much benefit. It's annoying as your application now likely have to support multiple versions of the API as well.
- dpark 11y agoVersion X.1 is not X+1. X.1 should contain no breaking changes. Otherwise your versioning is useless. If any change to the version number implies breaking changes, then you could replace the version with Rand() and it would do the same. If you're shipping versions like X.Y.Z for 3rd parties to consume, you should learn to use those minor and patch versions meaningfully.