Glassbathroom said:
I really think that if we had a Rosetta for Windows or dual booting, then many many people would be reassured and switch. Once the percentages of Mac users has increased substancially, as I am sure it would, software companies like AutoDesk would take the section of the market much more seriously and port their products properly.
Here is the thing that troubles me about that argument... it was the same argument put forward when Apple originally introduced Carbon.
Originally what was to become Mac OS X was going to have two environments: Yellow Box (which is now Cocoa, and which was able to use either Objective C or Java) and Blue Box (which became
Classic for running older Mac apps).
Developers (like Microsoft, Adobe, Macromedia, etc.) told Apple that they didn't want to rewrite their apps for the new operating system*. So Apple decided that they would include another environment based on the original Mac APIs that would let developers move their apps without completely rewriting their code. The idea was that once Mac OS X had a substantial user base and these developers saw what Cocoa could do first hand, that they would eventually convert their existing apps to Cocoa.
This hasn't happened. These developers have had no reason to move and so they haven't left Carbon. There are far more advantages in the Cocoa environment today than at any point in it's history, and they still have no reason to switch.
To a degree (from a person who has used the Cocoa environment in all it's forms over the years) Carbon applications seem as isolated from the advantages of Mac OS X as Windows apps would be in a
Rosetta for Windows. And if developers are given a
Rosetta for Windows, I'm quite sure that like Carbon developers, they would say that that is
good enough and stop there.
Anything that quiets the users to any degree is what most developers are willing to take steps to do. And a
Rosetta for Windows type of thing would be more than enough to kill any ideas they might have had towards actually making a true Mac version. That type of step takes the pressure off developers rather than putting the pressure on them.
If you want AutoDesk for Mac... get people together to make a lot of noise about it. The platform has survived this long because of campaigns like that.
*
Note: Developers told Apple the same thing during the development of Copland and Apple had started building an environment based on the original Mac APIs. It was from this that Carbon came from... which was Apple was able to have AppleWorks 5 and Adobe was able to have Photoshop 5 running in Carbon on Rhapsody at WWDC 98 only a few weeks after deciding to go with Carbon to appease developers.