3 ms·
Compiling Objective-C on Windows is not such a big deal. The huge thing here is that Microsoft has apparently reimplemented the Apple frameworks, because that's
by pavlov 12y ago
Compiling Objective-C on Windows is not such a big deal. The huge thing here is that Microsoft has apparently reimplemented the Apple frameworks, because that's the only way they could port over existing iOS code.
I'm extremely curious to find out how much of UIKit is available on Windows Phone. It might be something disappointing like "well, if you stick to old pre-iOS7 methods and don't use new frameworks or AVFoundation or anything, most of your code will compile"... If they're really tracking the latest iOS on this, it's an amazing feat.
It's worth noting that Microsoft also has a companion product for Android, the "Universal Windows Platform Bridge for the Android Runtime" a.k.a. Project Astoria:
https://dev.windows.com/en-us/uwp-bridges/project-astoria https://dev.windows.com/en-us/uwp-bridges/project-astoria
The difference seems to be that the iOS porting toolkit is an SDK, while the Android version is a complete runtime. So you can take an existing Android app (.apk file) and run it directly on Windows Phone, whereas the iOS app will need to be recompiled in Visual Studio.
I find the Android bridge to be the really exciting news. Now every phone vendor except Apple supports Android apps! I wrote a blog post about it a few days ago when it was announced:
http://blog.neonto.com/2015/04/29/android-is-the-new-win32-the-new-java-and-the-new-flash/ http://blog.neonto.com/2015/04/29/android-is-the-new-win32-t...
- sudioStudio64 12y agoIts not exactly as you describe. The android support is just like the IOS support. You have to rebuild your app for it. Still pretty neat, but it is a recompile. Here's more info: http://www.slashgear.com/video-project-astoria-microsofts-android-app-porting-tool-at-work-01381744/ http://www.slashgear.com/video-project-astoria-microsofts-an...
- pavlov 12y agoThanks for the link! It seems to me that you don't have to compile your app in Visual Studio, though? The video on the Project Astoria page shows an Android app being built for Windows Store using Eclipse on a Mac. That's a key difference compared to the iOS support. To port an iOS app to Windows, you need to build it in Visual Studio. To port an Android app to Windows, you use your existing toolchain and just produce another .apk with some different dependencies.
- bernadus_edwin 12y agoI saw project astoria first time on nokia X website developer. It seems microsoft keep continue the project and re marketing again and call it universal windows app. If you have apk file and not connect to google service, all you need is just upload it from the website. And also if you change the icon asset, people almost cannot see the different
- yconst 12y agoA related thought might be, once this is in place, how much work would it be so support Appkit (OS X) apps as well?
- pavlov 12y agoThe weird thing is that such a product -- AppKit on Windows -- existed and was made by Apple itself. It was called "Yellow Box for Windows" and shipped as part of WebObjects at one point. Now the tables are turned, and Microsoft is building an "iOS Yellow Box" of their own.
- lukeh 12y agoIndeed. Tell any ex-NeXT person circa 1996 that MS would be effectively building their own OPENSTEP for Windows and no one would have believed you. Will be interesting see how they implemented it and whether they used Apportable's Foundation (which looks really well written).
- pavlov 12y agoI wonder if part of the reason for last year's Swift announcement was that Apple got whiff of Microsoft's Obj-C Cocoa clone. Swift was obviously half-baked when it came out. It's still far from production quality IMHO. But as a deterrent for this kind of compatibility action, Swift's existence is quite effective.
- dep_b 12y ago- Swift uses the same compilers and frameworks - Swift support s in Xcode and if Microsoft doesn't watch out their implementation might be miles ahead at their first try - Swift 1.0 was a marketing 1.0, technically maybe a 0.2 release. I hope I don't need to touch it again in the next year even though I like the language principally
- lindig 12y agoWhile technically impressive, I wonder how much economical sense does it make for an iOS developer to go this route. For a small install base you open up a support front and now your code needs to work against the UIKit implementation of Windows Phone that by all likelihood will have its own bugs and limitations. You also might have planned to use Swift on iOS and this isn't possible when you want to compile your code for Windows Phone. Edit: I meant to talk about Swift, not Swipe.
- bernadus_edwin 12y agoSince microsoft remake the UIKit, theoriticaly it still support swipe. Well at least you can swipe on ui table view.
- mcintyre1994 12y agoIs there any likely technical reason Microsoft won't be able to do the same with Swift in the future? As I understand (not an Apple developer) doesn't it use the same frameworks, so they can reuse that? Its syntax also looks way more similar to c# than obj c does from a quick look.
- MikusR 12y agoIt seems to be in the works as during the Build talk there was a "suit" that kept saying "no comments" when asked about Swift.
- CHY872 12y agoThe technical reason is probably that Obj-C has multiple stable implementations (which agree almost entirely), the GNU or Clang frontends, which makes it easy to write your own implementation because you can study what those two do (in the worst case; the Obj-C part they could just do by compiling either of those two compilers). With Swift, the compiler is closed source, so you either have to examine the code it produces or the programmers manual, which is legitimately more difficult technically. Then there's the fact that the lawyers will have to be all over any Swift implementation, and it gets even harder. None of this would have happened if Clang didn't exist :P The whole reason that Microsoft can do this project now is because Clang didn't exist when Apple/NeXT started development on Obj-C.
- supercoder 12y agoFor games this approach can make a lot of sense, for other types of apps that make heavy use of UIKit it's certainly worth considering if it's the best approach.