3 ms·
Amazing that Apple introduced a breaking change in a .4 release. Probably a mistake? Also amazing it wasn't caught during the beta period.
by pier25 3y ago
Amazing that Apple introduced a breaking change in a .4 release. Probably a mistake?
Also amazing it wasn't caught during the beta period.
- mvdtnz 3y agoThis kind of behaviour is very common from Apple.
- goosedragons 3y agoIt wasn't in the public beta according to Oracle.
- empthought 3y agoApple has never been a follower of semantic versioning.
- lloeki 3y agonitpick: Apple doesn't follow SemVer 2.0, but they do have a semantic versioning scheme, that is, the version components carry a certain semantic, it's just so that this semantic is different than the semantic defined by the SemVer 2.0 specification. One can have any sort of semantic versioning that is not SemVer 2.0 compliant and still be useful, see e.g Rails or Ruby. Even .Net assemblies are not SemVer 2.0 compliant: their pattern is maj.min.patch.build but SemVer 2.0 specifies that there can only be three conponents and build info must be behind a plus, like maj.min.patch+build