Linked by Thom Holwerda on Sat 2nd May 2015 21:49 UTC

Steven Troughton-Smith has been looking into the how and what behind Microsoft's ability to compile Objective-C code for Windows 10, and the history of it all is interesting. It turns out that Microsoft's current implementation was initially developed by a company called Inception Mobile for BlackBerryOS 10. It took iOS Objective-C and converted as much as possible to Java or C++, hooking into the native platform APIs. It still works similarly on Windows 10.

After trying to woo BlackBerry, Inception Mobile tried to shop it around to Samsung for its Tizen platform. The audio file of the company's presentation at the Tizen Developer Conference 2013 is still available, too.

Eventually, as we know now, Inception Mobile was acquired by Microsoft, and its co-founder Salmaan Ahmed ended up at Microsoft. And lo and behold: Ahmed was a speaker at this year's Build conference, under the title "Compiling Objective-C Using the Visual Studio 2015 C++ Code Generation that Builds Windows, SQL, .Net, and Office".

In other words, this technology has been in development for a long time, and looking at the slides and listening to the presentation from the past few years indicates that the technology was platform-agnostic, working on BlackBerryOS, Tizen, Android, and now Windows.

Very interesting. Apparently BlackBerry and Samsung saw no real value in this technology - at least, not enough to acquire it or include it in their platforms, whereas Microsoft jumped on it and turned it into a big deal for Windows 10.

Permalink for comment 610126
To read all comments associated with this story, please click here.
Comment by Sidux
by Sidux on Mon 4th May 2015 06:15 UTC
Member since:

That's great news and I do hope Microsoft will put it to good use, having all the experience they earned until now.
The Windows Phone story always puzzled me.
There are so many die hard .NET developers I know that actually prefer struggling with Xamarin or other decent .NET interpreters to make the code available on iOS and Android that could start building apps on Windows Phone first but that does never happen aside from a small hobby.
It's not like Windows Phone is a mess, and this does come from someone who used Nexus devices for 4 years. Almost 90% of basic apps that I need to run on a phone are there and work decent enough.
The problem Microsoft has to fix is open up the Windows Phone development process. In its current state is not exactly an easy process (or as easy anyone can go around starting iOS or Android development).
Couple this with the very different UI logic that is on Windows Phone and you have the recipe of "disaster".
As good or unique it is, unfortunately Microsoft was very late to the party and the only way they could "mix in" is by house standards.

Reply Score: 2