Comment by mattparcher | Hacker News Reader

Comment by mattparcher | Hacker News Reader

Parent Full thread

(I understand that you’re probably being somewhat sarcastic, but for the sake of semantics…)

It’s pretty clear by the amount of change (and Apple’s marketing efforts) that each OS 10.#.0 release is a "major" OS update, on par with the relative significance of each iOS #.0 release.

But Gruber may have over-generalized here. Indeed, Apple has added major new features in iOS .# updates, e.g. AirPlay and AirPrint in 4.2, or the Personal Hotspot feature in 4.3.

What they haven’t done is change key functionality in a point update, let alone introduce regressions. (In fact, before this incident, I’m struggling to recall Apple ever removing/crippling existing functionality.) If they were going to perform a full Maps switch-out, maybe they felt that now would be the best time, if only because there is so much positive press out there to temper the backlash.

Edit: Regarding removed features, I was mostly thinking of Apple’s record with iOS. As gurkendoktor points out, they have certainly removed ("simplified") functionality in Mac OS X, often creating great frustration.

My tongue is firmly in cheek, yes. I'm poking fun at the silliness of attaching some holy meaning to version numbers.

My point is that version numbers for end-user software are borderline meaningless; they're marketing fodder. Just look at Chrome and Firefox, for example. Firefox didn't suddenly start improving 10x faster than it was before, but they changed their versioning scheme in a marketing play to compete with Chrome's ever-inflating version, as the casual user assumes that Chrome 37 must be much better than Firefox 6 because its major version is so much bigger.

Apple could either ship a regression in a new major, or ship a less broken regression in a new minor. In either case, there's going to be a regression. Regressions are unfortunate anytime they have to happen, but the assertion that you could only replace Google Maps with an in-house solution in a major is just silly post-hoc justification. You can't avoid disappointing users except by not shipping a regression at all, but you can lessen it by shipping a less-broken product.

As an aside, I can think of at least one other major breaking change/regression in a point release - the total swap in functionality of the lock/mute switch in iOS 4.2. There are also things like dropping support for older devices in point releases (4.3 dropped support for the iPhone 3G) that make the argument look even weaker; device deprecation is generally the sort of thing that is sacredly reserved for major releases, yet Apple seems to have had no problem doing it in a point release, and we're supposed to believe that yet somehow Apple wasn't willing to replace an app in a point release just because it isn't a major?

> In fact, before this incident, I’m struggling to recall Apple ever removing/crippling existing functionality

Mac OS X has had plenty of that. You buy a Mac Mini with a remote so you can use Front Row, and bam, Front Row's gone. But that is probably why Mac users are a lot more careful with updating their systems than iOS users are/were.

Reply on news.ycombinator.com