Snow Leopard natively running any 32bit Windows application - without the need for a Windows license.
1.) Might not impact Apple software market that much
If Apple touts the 64bit card for native Mac applications, there's still a market for Mac specific apps - anything that's 64bit.
Even on the Windows side everyone is moving to 64bit. Assuming that Apple's MS license doesn't cover 64bit code, it would be easy to see that this would not run all new 64bit apps, but would give users a nice transition to run most of their older 32bit Windows apps.
2.) Windows games support (?)
I would assume most Windows games are still 32 bit, even latest releases.
The Mac gaming market is not that huge, and most of the newer titles are actually cross-compiled games, not natively programmed for OSX and hence often slower than the Windows verison on comparable Windows machines. Perhaps Snow Leopard is able to actually run original 32bit Windows games faster than those cross-compiled 'Mac' games.
This could potentially destroy the nascent Mac gaming market, but it would in one fell swoop remove the 'not enough games on the Macs' argument.
But I'm only speculating here, not sure that compatibility layer would run games sufficiently well.
3.) Microsoft Office
Apple constantly has this fear of Microsoft stopping development of MS Office for Mac. Now imagine that would go away completely as users could always run the Windows version.
Sure eventually most Windows PCs would be 64bit and then we're back where we started, but it will be a while until MS can offer a 64bit only version and no longer offer backwards compatible 32bit versions.
Especially since most netbooks are 32bit, MS Office 32bit will be around for quite some years.
4.) Business users
Many corporations use custom developed Windows software. To run these on a Mac each user would have to also own a license of Windows and a license of Parallels or VM Ware. With several dozen or hundreds of machines this gets expensive fast - also in support costs. Apart from the fact that the hardware already needs better specs to run virtualization software.
Now imagine they could just buy a low end Mac and their proprietary software would still just run!
A huge stumbling block removed from Macs not being adopted in the business world.
As long as Apple can sell this as 'migration argument' where old, 32bit legacy applications would run - while modern software would all be Mac-only and 64bit, I don't see this too much of a danger for Mac software developers.
This could work.
It's still a risk though.
What if only 90% of the Win software works? Most of these arguments wouldn't really be full arguments.
What if OSX just becomes another 'ancient Windows platform'.
What if only 90% of the Win software works? Most of these arguments wouldn't really be full arguments.
This is the crux of the whole argument, I think. I mean, this is why CrossOver hasn't taken off. It is totally BADA** for stuff like running Office (If you haven't tried it believe me it works and is much much better than Parallels) but it's extremely touch and go with anything else, as a result you can't just recommend it to people unqualified like you can with Parallels.
Snow Leopard natively running any 32bit Windows application - without the need for a Windows license.
1.) Might not impact Apple software market that much
If Apple touts the 64bit card for native Mac applications, there's still a market for Mac specific apps - anything that's 64bit.
Even on the Windows side everyone is moving to 64bit. Assuming that Apple's MS license doesn't cover 64bit code, it would be easy to see that this would not run all new 64bit apps, but would give users a nice transition to run most of their older 32bit Windows apps.
This actually doesn't sound bad. Think of how many Windows users plan on buying a new computer to take advantage of 64 bit computing - This could actually be a solid opportunity for switchers.
Wouldn't such a scenario push win32 development as the default cross-platform development method? Want a program running on mac and windows, develop a win32 app. The opposite way would just be as interesting (providing a compatibility layer to run OS X apps on windows). Or even better, let linux GTK/QT apps run natively, being friends with the open-source community is a good thing.
Also, Apple is working hard to ge a unified look in OS X, and now they are letting ugly windows apps run accross their system?
I really can see the use and the profit (buy a mac, and u get both worlds natively). Nevertheless, to me thats not a game-changer and I sincerely hope this is not the big thing. To me this brings nothing 'new', it brings old stuff a different way. I'd be more impressed if they came with the whole 'home-server' idea, way more useful!
ExOne outstanding query on my part would be about the prospect for the future if Apple went down this path. If they built in some kind of compatibility layer for Win XP and even Vista, but then could not continue it for Win7 and/or beyond, it could turn into a bit of a complicated mess for end-users. In the long run it might be better to just not get into the area at all, rather than get expectations up and not be able to deliver.
Thoughts?
They only have a license for stuff up to 2002 so they can't go beyond XP. For most things they wouldn't need to though. It was a cross-license too so Microsoft have some of Apple's stuff. This may explain why Vista has some things similar to OS X. I'm not sure how much stuff each of the cross-licenses cover.
Quote:
Originally Posted by hobBit
This could potentially destroy the nascent Mac gaming market, but it would in one fell swoop remove the 'not enough games on the Macs' argument.
Yep, it sort of defeats the purpose of the 10 or so good Mac games there are but can bring in thousands. I'm not sure how low level they could go though regarding drivers and things. Crossover for example doesn't touch things like USB support and optical disc protection.
Quote:
Originally Posted by hobBit
What if only 90% of the Win software works? Most of these arguments wouldn't really be full arguments.
What if OSX just becomes another 'ancient Windows platform'.
I see it as being like PPC OS X's classic environment. A way to offer compatibility while people migrate their software to a newer operating system. It would only matter if the 10% of software left was stuff worth running. For example, I doubt that NTFS filesystem software is needed. If there was an important software package like AutoCAD that didn't run, just like Crossover, Apple could put more attention into making specific apps work. Crossover had special effort put in to make Half-Life 2 run and you can tell as it runs almost perfectly, whereas other, simpler but less important games don't.
Most manufacturers aim for XP compatibility as they are aware of the problems with Vista so very few software packages are Vista-only. The same kinda goes for stuff pre-XP. If they nail XP compatibility, it covers a huge amount of software.
They only have a license for stuff up to 2002 so they can't go beyond XP. For most things they wouldn't need to though. ... If they nail XP compatibility, it covers a huge amount of software.
Bingo. They don't need to have full on compatibility with Vista apps, they only have to have *legacy* compatibility for Win32 apps, to remove a huge barrier to adoption for a large number of folks tied to Windows.
With MS deprecating Win32 in favor of .NET, they're moving on as well. Providing a Win32 foundation would no longer create a "Well, we'll just use Win32 and get both platforms" situation, as the MS ecosystem doesn't really want to support them either.
But, for those corporations or installations that have that one legacy custom app that they can *NOT* do without (and there are a huge number of them), if Apple can say "No problem, keep using it", then those companies now have another option to consider. That alone would be a big deal - if even 5% of those decided to switch, that's new market.
Not to mention all the folks who have hung onto an old PC just to run that odd app or game...
If running Windows apps in Os X is what Ireland is talking about and it is correct, I just want to go on record that I predicted this back in 2004.... http://forums.appleinsider.com/showthread.php?t=46136 I think I may have even posted more about it earlier, but God its embarrassing to reread old threads. In fact the very first rumblings of this go all the way back to Steve's return. MacWeek reported it was one of the goals the board had for Rhapsody.
In most cases, software companies do not spend millions of dollars in R&D and then give the software away free on new computers (or sell it for only 120). The operating system business is VERY VERY different than any other kind of software company.
I think we agree then, software companies in general do indeed have higher gross margins, hence, Apple's margins may indeed be higher on software than on their hardware.
Quote:
Originally Posted by Amorph
...
For the first time in the roughly 150 million year history of the Clone Wars I can see a bit of a case for limited cloning, but not enough to justify it. Just for fun, I'll spell out what I see.
....Now, look at the conference call results: Desktop sales are in free fall, plunging 25%, but laptop sales more than made up for it, and Mac sales actually increased year over year. Laptops accounted for 71% of all Macs sold this past quarter. I assume that Apple is frantically evaluating its desktop strategy to see what can be done about this, but I think they realize that the desktop is becoming a niche product.
......
It almost seems that Apple's strategy is just that. let Apple desktop sales decline to a point that they exit the market and eventually only allow selected OEMs to manufacture desktops that are licensed to run Mac OS. Nawww, it only seems that way, I just can't see Apple doing this. yet ?
Wouldn't such a scenario push win32 development as the default cross-platform development method?
Yes.
It would completely undermine OS X as a software development platform.
You could achieve perfect compatibility by stopping OS X development completely and switching the Mac over to Windows.
There is very little prospect for an increase in market share based on being a hardware vendor. Especially when the vehicle is Apple's highly profitable top-end hardware.
In software however, the prospect for growth is massive.
Just letting Windows apps run on OSX straight-forward doesn't really seem like such a good idea to me...
Making cross-platform coding easier however, would benefit the Mac. But seeing as Apple is heavily pushing towards Cocoa with it's own developers, I don't know... Perhaps a Win32/.NET C#-Cocoa binding layer or something like that?
The fabled 'Red Box' Windows compatibility layer, kept haunting the Apple world since the days before OSX.
If Apple truly has a license to use Win32 code, that license's value is fading fast. 5 or 10 years from now, it is hardly worth anything. Making use of it now is better than tomorrow.
However, the main concern was always: will this kill OSX software development.
And it would.
But since Win32 is even fading in the Windows world it is a 'killer with a built-in timer'. And as such becomes merely a migration assistant for legacy Windows code.
And that is the only way Apple can play this safely.
In a worse-case scenario Microsoft as a result will push 64bit application development even more and business will be faced with either migrating to Apple or sticking with Microsoft and then migrate to 64bit. Since 64bit Windows software development is probably an easier migration path from 32bit Windows software than once migrated to Apple having to learn Apple software development - chances are most businesses will go the 64bit Windows route, and the effectiveness of this 'Red Box' in OSX will fade quickly.
For this to really work Apple should think another step ahead and provide easy software development / migration tools too. Making a case that starting a software project in OSX is easier than transition 32bit Windows code to 64bit Windows code. If that is ever achievable...
It would completely undermine OS X as a software development platform.
You could achieve perfect compatibility by stopping OS X development completely and switching the Mac over to Windows.
There is very little prospect for an increase in market share based on being a hardware vendor. Especially when the vehicle is Apple's highly profitable top-end hardware.
In software however, the prospect for growth is massive.
C.
Please, stop talking. You make no sense. And you just keep repeating the same ridiculous things again and again in the face of proof after proof.
It would completely undermine OS X as a software development platform.
You could achieve perfect compatibility by stopping OS X development completely and switching the Mac over to Windows.
It could be more of a development layer than runtime.
This is how WINE achieves the best compatibility.
Instead of developers licensing tools from Transgaming or whatever setup they use, Apple could bundle the same thing as part of XCode.
Huge companies have a ton of legacy code mired with all sorts of Windows specific code. The effort/reward ratio for doing a solid port to the Mac is probably too high for a lot of companies to bother about.
Adding API compatibility removes a lot of effort. It means we can expect simultaneous Mac/Windows game releases for all future games as it will mean little more than a compile on any Mac with XCode.
This wouldn't encourage users who already have a code-base built for the Mac to switch to Windows APIs, especially big companies who know the importance of native code and code that isn't run from a compatibility layer, which has no guarantee of future support and feature development.
As for new developers, it may discourage them from bothering with Mac-specific development but who's to say the alternative wouldn't simply have been no Mac compatibility at all?
I would rather be able to run 3DS Max through a compatibility layer than under VMWare, Parallels or Bootcamp and be able to use Photoshop for the Mac alongside.
As people have seen from the games that already use Transgaming's Cider, you really don't notice that you're not running a native Mac app. It's true that games are different as they tend to have custom interfaces built on the graphics layer but I don't see why Apple couldn't override the interface calls to native ones so that Windows apps just appear to be Mac apps.
Move window-level menus up to the main menu when that window is in focus and add aqua/marble theme to the windows and run all the processing code through the compatibility layer.
Apple has addressed the needs of switchers who require some Windows compatibility.
It is called Boot Camp.
Furthermore VMWare, Parallels and Crossware have added their versions. And Microsoft have kindly provided a Mac native version of Office.
The Mac is awash with Windows welcome mats.
If Mac sales are being held back by the lack of even more Windows compatibility then OS X should be abandoned. Because after all - according to Meelah - Apple is a hardware company.
OS X needs to attract more developers, not less. And that means it's far more important to get OS X programs onto more PCs -than get Windows programs running on Macs.
OS X needs to be installed on more computers than the handful of boutique lines that Apple sells.
Dissatisfaction in Vista, plagues of Windows worms and a stagnating PC desktop market are all reasons for Apple to undertake an aggressive OS land-grab.
Apple has addressed the needs of switchers who require some Windows compatibility.
Not really because you have to run Windows and buy a Windows license to run Windows software. As I say, a lot of companies have a ton of legacy code that they are in no hurry to port to Mac APIs so the deal is that Mac users will likely never get these apps without Windows API compatibility.
Mac users want some Windows software but not the Windows OS baggage and filesystem that comes along with it.
OS X has been out for 9 years now and still no sign of certain major industry-standard apps coming over. Do we just wait until they decide to hire Cocoa developers? We could be waiting indefinitely.
Look at the amount of Carbon apps vs Cocoa, if Apple don't make the development environment attractive, why should developers move? Part of the problem is pushing Objective-C. Relatively few developers are familiar with this language so it's not getting a rapid uptake. I'm sure iphone development will help but that's a very new platform.
Take for example, DirectX and OpenGL on Windows. You could have said that Microsoft including OpenGL APIs would automatically mean DirectX development would die out. Far from it. If DirectX offers more features or better development, developers will go for it to make their software the best. If developers find that Objective-C/Cocoa development isn't good for them, give them the option to use other APIs.
Eventually, we will all likely run apps with operating systems running transparently in the background and you won't even care if it's Linux, Windows or Mac APIs because in the end, it's all about the apps.
Think more strategically. Apple has no desire to help users troubleshoot installing crappy windows software on OS X. Leave that to Parallels, etc., and open source efforts are also catching up. There's no need for Apple to make a contribution here.
Coding with Xcode and Objective-C is already far superior and streamlined compared to Windows, especially when you consider all of Apple's Core functions (CoreAudio,CoreImage,CoreData,CoreAnimation,etc.).
Whether you like it or not, Microsoft is catching up to user interface features in OS X. Apple needs to trump Windows in their home court.
What Apple needs to do is make it easier for people to be able to justify purchase of their hardware. WebKit is one example where, by Apple making it easy for developers to take advantage of their efforts, Apple has repositioned itself as the leader of mobile web browsing.
what Apple will do, what the "big" thing is that will jaw drop your socks off is open up their ability to seamlessly deliver any and all Xcode applications to Windows for all OS X Developers. This will have several effects:
1) Open up a huge consumer market for OS X Programmers, dramatically snowballing the growing developer community
2) Help move Xcode toward the centerpoint of OS software development, giving apple more power similar to the WebKit story
3) Bring more programmers to Xcode, thus selling more Macs (Xcode will remain OS X only, for both technical and strategic reasons)
4) The user experience will still be superior on OS X since Apple can integrate things like AddressBook, iCal, etc. which will not be available for integration on Windows. So certain features will be "Mac Only". This will help to stimulate consumers to upgrade to Mac hardware.
Apple will be positioning Xcode to be the centerpoint for all OS deployment: OS X, iPhone, Windows, YourFavoriteOSHere.
step 5) Profit.
Apple has been moving in this direction for a while now, and we all know Xcode already has this ability (as done for iTunes & Safari). All Apple has to do is flip the switch to enable it for all developers.
It's minimal effort on their part, while still protecting the Apple brand and helping them to redefine the user experience on all platforms. Apple will gain greater mind share among user interface development, while continuing to patent these conventions, thus further protecting their brand. The fact that developer software can run on other platforms will only make dynamic use of CoreFeatures in OS X that much harder to give up by switching back to Windows-only development. Developers will see how much more dynamic their applications can be in OS X, and more people will be hooked on OS X development and never look back...
what Apple will do, what the "big" thing is that will jaw drop your socks off is open up their ability to seamlessly deliver any and all Xcode applications to Windows for all OS X Developers. This will have several effects:
Rumors of the so-called YellowBox technology has been floating around for a few years now. It could certainly attract some developers and allow them to write one program - and reach a much much wider audience.
But I don't see how you get to...
Quote:
Originally Posted by hymie
step 5) Profit.
It benefits developers more than it benefits Apple. Apple will only profit if computer buyers switch to Mac. And with YellowBox - it could argued that the reason to switch is a bit less.
Perhaps if Apple opened an AppStore and this included Windows executables. It might generate a revenue.
when is this due to hit? Snow Leopard is ready by all accounts. It will hardly be this month given there's a lead in time to apple events to give the press notice etc.
Comments
Snow Leopard natively running any 32bit Windows application - without the need for a Windows license.
1.) Might not impact Apple software market that much
If Apple touts the 64bit card for native Mac applications, there's still a market for Mac specific apps - anything that's 64bit.
Even on the Windows side everyone is moving to 64bit. Assuming that Apple's MS license doesn't cover 64bit code, it would be easy to see that this would not run all new 64bit apps, but would give users a nice transition to run most of their older 32bit Windows apps.
2.) Windows games support (?)
I would assume most Windows games are still 32 bit, even latest releases.
The Mac gaming market is not that huge, and most of the newer titles are actually cross-compiled games, not natively programmed for OSX and hence often slower than the Windows verison on comparable Windows machines. Perhaps Snow Leopard is able to actually run original 32bit Windows games faster than those cross-compiled 'Mac' games.
This could potentially destroy the nascent Mac gaming market, but it would in one fell swoop remove the 'not enough games on the Macs' argument.
But I'm only speculating here, not sure that compatibility layer would run games sufficiently well.
3.) Microsoft Office
Apple constantly has this fear of Microsoft stopping development of MS Office for Mac. Now imagine that would go away completely as users could always run the Windows version.
Sure eventually most Windows PCs would be 64bit and then we're back where we started, but it will be a while until MS can offer a 64bit only version and no longer offer backwards compatible 32bit versions.
Especially since most netbooks are 32bit, MS Office 32bit will be around for quite some years.
4.) Business users
Many corporations use custom developed Windows software. To run these on a Mac each user would have to also own a license of Windows and a license of Parallels or VM Ware. With several dozen or hundreds of machines this gets expensive fast - also in support costs. Apart from the fact that the hardware already needs better specs to run virtualization software.
Now imagine they could just buy a low end Mac and their proprietary software would still just run!
A huge stumbling block removed from Macs not being adopted in the business world.
As long as Apple can sell this as 'migration argument' where old, 32bit legacy applications would run - while modern software would all be Mac-only and 64bit, I don't see this too much of a danger for Mac software developers.
This could work.
It's still a risk though.
What if only 90% of the Win software works? Most of these arguments wouldn't really be full arguments.
What if OSX just becomes another 'ancient Windows platform'.
What if only 90% of the Win software works? Most of these arguments wouldn't really be full arguments.
This is the crux of the whole argument, I think. I mean, this is why CrossOver hasn't taken off. It is totally BADA** for stuff like running Office (If you haven't tried it believe me it works and is much much better than Parallels) but it's extremely touch and go with anything else, as a result you can't just recommend it to people unqualified like you can with Parallels.
Now this could actually work!
Snow Leopard natively running any 32bit Windows application - without the need for a Windows license.
1.) Might not impact Apple software market that much
If Apple touts the 64bit card for native Mac applications, there's still a market for Mac specific apps - anything that's 64bit.
Even on the Windows side everyone is moving to 64bit. Assuming that Apple's MS license doesn't cover 64bit code, it would be easy to see that this would not run all new 64bit apps, but would give users a nice transition to run most of their older 32bit Windows apps.
This actually doesn't sound bad. Think of how many Windows users plan on buying a new computer to take advantage of 64 bit computing - This could actually be a solid opportunity for switchers.
Also, Apple is working hard to ge a unified look in OS X, and now they are letting ugly windows apps run accross their system?
I really can see the use and the profit (buy a mac, and u get both worlds natively). Nevertheless, to me thats not a game-changer and I sincerely hope this is not the big thing. To me this brings nothing 'new', it brings old stuff a different way. I'd be more impressed if they came with the whole 'home-server' idea, way more useful!
ExOne outstanding query on my part would be about the prospect for the future if Apple went down this path. If they built in some kind of compatibility layer for Win XP and even Vista, but then could not continue it for Win7 and/or beyond, it could turn into a bit of a complicated mess for end-users. In the long run it might be better to just not get into the area at all, rather than get expectations up and not be able to deliver.
Thoughts?
They only have a license for stuff up to 2002 so they can't go beyond XP. For most things they wouldn't need to though. It was a cross-license too so Microsoft have some of Apple's stuff. This may explain why Vista has some things similar to OS X. I'm not sure how much stuff each of the cross-licenses cover.
This could potentially destroy the nascent Mac gaming market, but it would in one fell swoop remove the 'not enough games on the Macs' argument.
Yep, it sort of defeats the purpose of the 10 or so good Mac games there are but can bring in thousands. I'm not sure how low level they could go though regarding drivers and things. Crossover for example doesn't touch things like USB support and optical disc protection.
What if only 90% of the Win software works? Most of these arguments wouldn't really be full arguments.
What if OSX just becomes another 'ancient Windows platform'.
I see it as being like PPC OS X's classic environment. A way to offer compatibility while people migrate their software to a newer operating system. It would only matter if the 10% of software left was stuff worth running. For example, I doubt that NTFS filesystem software is needed. If there was an important software package like AutoCAD that didn't run, just like Crossover, Apple could put more attention into making specific apps work. Crossover had special effort put in to make Half-Life 2 run and you can tell as it runs almost perfectly, whereas other, simpler but less important games don't.
Most manufacturers aim for XP compatibility as they are aware of the problems with Vista so very few software packages are Vista-only. The same kinda goes for stuff pre-XP. If they nail XP compatibility, it covers a huge amount of software.
They only have a license for stuff up to 2002 so they can't go beyond XP. For most things they wouldn't need to though. ... If they nail XP compatibility, it covers a huge amount of software.
Bingo. They don't need to have full on compatibility with Vista apps, they only have to have *legacy* compatibility for Win32 apps, to remove a huge barrier to adoption for a large number of folks tied to Windows.
With MS deprecating Win32 in favor of .NET, they're moving on as well. Providing a Win32 foundation would no longer create a "Well, we'll just use Win32 and get both platforms" situation, as the MS ecosystem doesn't really want to support them either.
But, for those corporations or installations that have that one legacy custom app that they can *NOT* do without (and there are a huge number of them), if Apple can say "No problem, keep using it", then those companies now have another option to consider. That alone would be a big deal - if even 5% of those decided to switch, that's new market.
Not to mention all the folks who have hung onto an old PC just to run that odd app or game...
In most cases, software companies do not spend millions of dollars in R&D and then give the software away free on new computers (or sell it for only 120). The operating system business is VERY VERY different than any other kind of software company.
I think we agree then, software companies in general do indeed have higher gross margins, hence, Apple's margins may indeed be higher on software than on their hardware.
...
For the first time in the roughly 150 million year history of the Clone Wars I can see a bit of a case for limited cloning, but not enough to justify it. Just for fun, I'll spell out what I see.
....Now, look at the conference call results: Desktop sales are in free fall, plunging 25%, but laptop sales more than made up for it, and Mac sales actually increased year over year. Laptops accounted for 71% of all Macs sold this past quarter. I assume that Apple is frantically evaluating its desktop strategy to see what can be done about this, but I think they realize that the desktop is becoming a niche product.
......
It almost seems that Apple's strategy is just that. let Apple desktop sales decline to a point that they exit the market and eventually only allow selected OEMs to manufacture desktops that are licensed to run Mac OS. Nawww, it only seems that way, I just can't see Apple doing this. yet ?
Wouldn't such a scenario push win32 development as the default cross-platform development method?
Yes.
It would completely undermine OS X as a software development platform.
You could achieve perfect compatibility by stopping OS X development completely and switching the Mac over to Windows.
There is very little prospect for an increase in market share based on being a hardware vendor. Especially when the vehicle is Apple's highly profitable top-end hardware.
In software however, the prospect for growth is massive.
C.
Making cross-platform coding easier however, would benefit the Mac. But seeing as Apple is heavily pushing towards Cocoa with it's own developers, I don't know... Perhaps a Win32/.NET C#-Cocoa binding layer or something like that?
If Apple truly has a license to use Win32 code, that license's value is fading fast. 5 or 10 years from now, it is hardly worth anything. Making use of it now is better than tomorrow.
However, the main concern was always: will this kill OSX software development.
And it would.
But since Win32 is even fading in the Windows world it is a 'killer with a built-in timer'. And as such becomes merely a migration assistant for legacy Windows code.
And that is the only way Apple can play this safely.
In a worse-case scenario Microsoft as a result will push 64bit application development even more and business will be faced with either migrating to Apple or sticking with Microsoft and then migrate to 64bit. Since 64bit Windows software development is probably an easier migration path from 32bit Windows software than once migrated to Apple having to learn Apple software development - chances are most businesses will go the 64bit Windows route, and the effectiveness of this 'Red Box' in OSX will fade quickly.
For this to really work Apple should think another step ahead and provide easy software development / migration tools too. Making a case that starting a software project in OSX is easier than transition 32bit Windows code to 64bit Windows code. If that is ever achievable...
Yes.
It would completely undermine OS X as a software development platform.
You could achieve perfect compatibility by stopping OS X development completely and switching the Mac over to Windows.
There is very little prospect for an increase in market share based on being a hardware vendor. Especially when the vehicle is Apple's highly profitable top-end hardware.
In software however, the prospect for growth is massive.
C.
Please, stop talking. You make no sense. And you just keep repeating the same ridiculous things again and again in the face of proof after proof.
It would completely undermine OS X as a software development platform.
You could achieve perfect compatibility by stopping OS X development completely and switching the Mac over to Windows.
It could be more of a development layer than runtime.
This is how WINE achieves the best compatibility.
Instead of developers licensing tools from Transgaming or whatever setup they use, Apple could bundle the same thing as part of XCode.
Huge companies have a ton of legacy code mired with all sorts of Windows specific code. The effort/reward ratio for doing a solid port to the Mac is probably too high for a lot of companies to bother about.
Adding API compatibility removes a lot of effort. It means we can expect simultaneous Mac/Windows game releases for all future games as it will mean little more than a compile on any Mac with XCode.
This wouldn't encourage users who already have a code-base built for the Mac to switch to Windows APIs, especially big companies who know the importance of native code and code that isn't run from a compatibility layer, which has no guarantee of future support and feature development.
As for new developers, it may discourage them from bothering with Mac-specific development but who's to say the alternative wouldn't simply have been no Mac compatibility at all?
I would rather be able to run 3DS Max through a compatibility layer than under VMWare, Parallels or Bootcamp and be able to use Photoshop for the Mac alongside.
As people have seen from the games that already use Transgaming's Cider, you really don't notice that you're not running a native Mac app. It's true that games are different as they tend to have custom interfaces built on the graphics layer but I don't see why Apple couldn't override the interface calls to native ones so that Windows apps just appear to be Mac apps.
Move window-level menus up to the main menu when that window is in focus and add aqua/marble theme to the windows and run all the processing code through the compatibility layer.
It is called Boot Camp.
Furthermore VMWare, Parallels and Crossware have added their versions. And Microsoft have kindly provided a Mac native version of Office.
The Mac is awash with Windows welcome mats.
If Mac sales are being held back by the lack of even more Windows compatibility then OS X should be abandoned. Because after all - according to Meelah - Apple is a hardware company.
http://www.pcmag.com/article2/0,1895,1925239,00.asp
I don't believe that's the right way forwards.
OS X needs to attract more developers, not less. And that means it's far more important to get OS X programs onto more PCs -than get Windows programs running on Macs.
OS X needs to be installed on more computers than the handful of boutique lines that Apple sells.
Dissatisfaction in Vista, plagues of Windows worms and a stagnating PC desktop market are all reasons for Apple to undertake an aggressive OS land-grab.
C.
Apple has addressed the needs of switchers who require some Windows compatibility.
Not really because you have to run Windows and buy a Windows license to run Windows software. As I say, a lot of companies have a ton of legacy code that they are in no hurry to port to Mac APIs so the deal is that Mac users will likely never get these apps without Windows API compatibility.
Mac users want some Windows software but not the Windows OS baggage and filesystem that comes along with it.
OS X has been out for 9 years now and still no sign of certain major industry-standard apps coming over. Do we just wait until they decide to hire Cocoa developers? We could be waiting indefinitely.
Look at the amount of Carbon apps vs Cocoa, if Apple don't make the development environment attractive, why should developers move? Part of the problem is pushing Objective-C. Relatively few developers are familiar with this language so it's not getting a rapid uptake. I'm sure iphone development will help but that's a very new platform.
Take for example, DirectX and OpenGL on Windows. You could have said that Microsoft including OpenGL APIs would automatically mean DirectX development would die out. Far from it. If DirectX offers more features or better development, developers will go for it to make their software the best. If developers find that Objective-C/Cocoa development isn't good for them, give them the option to use other APIs.
Eventually, we will all likely run apps with operating systems running transparently in the background and you won't even care if it's Linux, Windows or Mac APIs because in the end, it's all about the apps.
Coding with Xcode and Objective-C is already far superior and streamlined compared to Windows, especially when you consider all of Apple's Core functions (CoreAudio,CoreImage,CoreData,CoreAnimation,etc.).
Whether you like it or not, Microsoft is catching up to user interface features in OS X. Apple needs to trump Windows in their home court.
What Apple needs to do is make it easier for people to be able to justify purchase of their hardware. WebKit is one example where, by Apple making it easy for developers to take advantage of their efforts, Apple has repositioned itself as the leader of mobile web browsing.
what Apple will do, what the "big" thing is that will jaw drop your socks off is open up their ability to seamlessly deliver any and all Xcode applications to Windows for all OS X Developers. This will have several effects:
1) Open up a huge consumer market for OS X Programmers, dramatically snowballing the growing developer community
2) Help move Xcode toward the centerpoint of OS software development, giving apple more power similar to the WebKit story
3) Bring more programmers to Xcode, thus selling more Macs (Xcode will remain OS X only, for both technical and strategic reasons)
4) The user experience will still be superior on OS X since Apple can integrate things like AddressBook, iCal, etc. which will not be available for integration on Windows. So certain features will be "Mac Only". This will help to stimulate consumers to upgrade to Mac hardware.
Apple will be positioning Xcode to be the centerpoint for all OS deployment: OS X, iPhone, Windows, YourFavoriteOSHere.
step 5) Profit.
Apple has been moving in this direction for a while now, and we all know Xcode already has this ability (as done for iTunes & Safari). All Apple has to do is flip the switch to enable it for all developers.
It's minimal effort on their part, while still protecting the Apple brand and helping them to redefine the user experience on all platforms. Apple will gain greater mind share among user interface development, while continuing to patent these conventions, thus further protecting their brand. The fact that developer software can run on other platforms will only make dynamic use of CoreFeatures in OS X that much harder to give up by switching back to Windows-only development. Developers will see how much more dynamic their applications can be in OS X, and more people will be hooked on OS X development and never look back...
If developers find that Objective-C/Cocoa development isn't good for them, give them the option to use other APIs.
Anyone who calls themselves a programmer can figure out Objective C in an afternoon. And Cocoa is a massive plus over MFC.
The reason developers are attracted to a platform is the REVENUE THEY MAKE from creating software. Development happens for commercial reasons.
The biggest deterrent to Mac development isn't the API.
It's the market share.
C.
what Apple will do, what the "big" thing is that will jaw drop your socks off is open up their ability to seamlessly deliver any and all Xcode applications to Windows for all OS X Developers. This will have several effects:
Rumors of the so-called YellowBox technology has been floating around for a few years now. It could certainly attract some developers and allow them to write one program - and reach a much much wider audience.
But I don't see how you get to...
step 5) Profit.
It benefits developers more than it benefits Apple. Apple will only profit if computer buyers switch to Mac. And with YellowBox - it could argued that the reason to switch is a bit less.
Perhaps if Apple opened an AppStore and this included Windows executables. It might generate a revenue.
C.
Snow Leopard is ready by all accounts.