Functional High Ground

I don’t think the situation is as dire for users as Marco makes it out to be, but I do agree that Apple should slow down. “It just works” was a great tagline, but if your products don’t live up to this ideal, it’s maddening.

Does all of this sound vaguely familiar? It should. Apple made similar pitches to developers during the run-up to Mac OS X Snow Leopard. Hitting the “pause” button on new features allowed Apple to shore up everything that had been put in place over the last few releases and make sure it worked well. Low level features don’t come into existence in the span of a year.1

It was a gamble, yes; but also (in retrospect) an easy sell. Like I said, we’ve been here before:

This was a risky strategy for Apple. After the rapid-fire updates of 10.1, 10.2, and 10.3 followed by the riot of new features and APIs in 10.4 and 10.5, could Apple really get away with calling a “time out?”

John Siracusa — Mac OS X 10.6 Snow Leopard: The Ars Technica review

Well, we know how that turned out.

Given all of the questions Apple has had to answer about their ability to continue to succeed with Tim Cook at the helm, I can think of no better way for the company to quiet the noise than to step back and publicly state their intentions. Apple has never put much stock into having the biggest marketshare and instead taken a “Damn the torpedoes” approach when it comes to the criticism2 they receive for this stance.

As others have said, there is reason to hope that things will work out. That this concern is little more than a bump in the road. Not a sign of impending disaster, but instead a clear sign that not all is well and something needs to change.

Certainly, Apple is different now and not the company it once was, I just hold out hope that there are still a few “Crazy Ones” left at 1 Infinite Loop who know how to weather the storm.

  1. Swift took 4 years. LLVM reached the 1.0 milestone in 2003.

  2. In Apple's case, it might be, "Damn the investors and pundits!"