Scott Steve on on why upcoming a are going Leopard-only

Scott Steve on, blogger of many things developer-related, has pe ed an in-depth explanation that a wers my a umptio as to why developers would (or should) go Leopard-only with their a .

The explanation Scott provides is pretty thorough, offering brief examples of what is so new and fancy in Leopard that would a eal to a developer. To be more ecific: Leopard offers some powerful tools and major changes in code that can really propel many a to be all they can be, and as Scott puts it: "Forgoing Leopard APIs until some arbitrary point in the future can actually hold the a back from its full potential."

A lot of the points Scott makes seem to boil down to a couple of fundamentals, with one of them being the tried and true mantra of "know your audience." Scott is right on when he points out that Mac users are Mac users by choice, which mea many of them who have a vested interest in 3rd party software (like TextMate and Delicious Library - both of which have a ounced future Leopard-only updates) are far more likely to be early adopter i.e. - they're also likely to be first in line for Leopard.

Even though he can roll with the devs, Scott writes in a language everyone can understand. His post is a great read if you're interested in the dynamics of why a Mac OS X developer would release an a on the bleeding edge of an OS update.

[via The A le Blog]