This is semi related tangent. I've worked in at a lot of software companies where they spent a lot of time being concerned about small groups of customers that

This is semi related tangent. I've worked in at a lot of software companies where they spent a lot of time being concerned about small groups of customers that were using old builds, how we would keep their setup working, etc. It always impresses me how Apple moves forward in spite of who may be left behind and I assume that this is a conscious choice they constantly have to revisit. The counter example would be Microsoft that still supported DOS for more than a decade after they moved on from it. I don't know any engineers who like maintaining legacy systems, so it seems to be a perk of working with Apple and I also think that this lack of concern for legacy is allowing Apple to move forward faster. At my last job every time a new project was requested by management I would ask, "What old project will we remove then? Because maintenance takes time." I pretty much never got an answer on that. It takes discipline to stay lean and to non-engineers legacy costs can be invisible a lot of times. One area where I see progress accelerating is XCode. You basically need to be running latest XCode to publish apps to the App Store, so people always run latest. On the other hand, I've got Visual Studio all the way back to 2003 on hand because clients don't want to take the time to upgrade. It drives me nuts. There's something satisfying about progress and something very depressing to me when I sit down to make changes to a project using Visual Studio 2003 .NET. Anyone know what I mean?