3 ms·
"Port Cocoa to Windows and port iTunes to Cococa" OpenStep was already ported Windows NT at one time ( http://en.wikipedia.org/wiki/File:OPENSTEP_on_Windows_NT
by wvenable 17y ago
"Port Cocoa to Windows and port iTunes to Cococa"
OpenStep was already ported Windows NT at one time ( http://en.wikipedia.org/wiki/File:OPENSTEP_on_Windows_NT.jpg http://en.wikipedia.org/wiki/File:OPENSTEP_on_Windows_NT.jpg ). They already port other libraries to Windows to support iTunes and Safari. I think this option makes the most sense moving forward if they want to continue building cross-platform applications.
- pyre 17y agoArguably iTunes is on Windows to support Windows users of iPhones/iPods (to expand their 'device market' beyond just the Mac ecosystem). Safari.... not really sure why Safari is there other than to try and support Windows developers of iPhone-targeted web-apps (before there was an official iPhone API). But that conclusion is questionable seeing how there are no Windows development tools for iPhone apps now that there is an official API. > They already port other libraries to Windows to support iTunes and Safari. iTunes doesn't use Cocoa/ObjC. It uses the Carbon/C (C++ too?) that was a way to transition between OS/9 and OSX back in the day (You could download the Carbon libraries for OS/9 and a Carbon app would run in OS/9 with them). Safari is Cocoa/ObjC so far as I know, but it's just a wrapper around Webkit for the most part. They could have ported the Windows version of Safari to Carbon, or just ported the parts of the Cocoa libraries that Safari needs (rather than the whole thing). So.... it looks something like this: Port X% of Cocoa to Win32 + Port iTunes to Cocoa Depending on that percentage and the amount of time it would take to port iTunes itself to Cocoa would determine how costly it is (time & money). I realize that you're also saying that porting however much of Cocoa over to Win32(+ Win64?) would help them develop more cross-platform apps, but I don't see this being part of their strategy. Unless you prescribe to the John C. Dvorák line of thinking that Apple is going to go cross-platform, make a way to seamlessly develope Windows/MacOS applications, and then eventually dump MacOS for Windows on Apple machines, I don't think that Apple will leave the galleon that they have for themselves (their product/developer ecosystem). They just use cross-platform apps as a means to an ends... extending gang planks to passing ships and beckoning their passengers to cross over to the Apple side (or at least buy their consumer-devices and get hooked onto those).
- wvenable 17y agoFrom what I've looked into, Safari on Windows isn't using Cocoa. The latest Safari even looks much more like a Windows application than previous versions. So maybe I'm wrong about this point. However, I still think they're going to have to port iTunes to Cocoa simply because they've essentially deprecated Carbon. For the Windows version of iTunes, maybe they'll just have an completely separate version that isn't a port.
- pyre 17y agoI know that when Safari for Windows first came out people were looking into some of the DLLs that were installed along with it, which were ports of things -- IIRC CF libraries at the very least -- from OSX. They may have depreciated those in newer versions due to poor compatibility with Windows.
- MikeCapone 17y ago> Safari.... not really sure why Safari is there other than to try and support Windows developers of iPhone-targeted web-apps (before there was an official iPhone API). My impression was that they ported Safari to window after they saw how much cash Mozilla was making from the embedded search fields. Probably doesn't hurt to also have one more way for potential Mac customers to dip their toe in the pool...
- pyre 17y agoWell that was another theory. When they first released it I saw these theories: * It's there to help encourage developers from Windows to write iPhone web apps. * It's there to help encourage web developers that use Windows to make their pages Safari/WebKit-compatible (because they don't have to own a Mac to test their pages against it). * It's there to foster 'switchers' by showing people that there are viable applications on the Mac (and that it's not a 'broken' platform). (e.g. the guy that sat behind me when I went to see 'White Noise' that kept complaining to his girlfriend that Michael Keaton was using a Mac and how much faster the audio processing that he -- Michael Keaton's character -- was doing would be going if he was on a PC with Windows) * It's the vanguard of Apple moving software to Windows to ditch OS X. * It's the the vanguard of Apple porting their core libraries to Windows to make running Windows apps under OS X native and seamless. (i.e. Apple + WINE or something like that) * It's their to drive up the number of Safari users to force better web standards. * Apple has no clue what they are doing. * Apple was using it as a way to make people excited and not bummed over the announcement that there would be no native API for developers on the iPhone. (Yes. It was released at that Keynote). Obviously some of these have proven false. As for the rest, it's a toss-up.