Microsoft's timing was the worst. I think they announced this a year after Swift was already announced, but before Swift was open sourced. So Microsoft wouldn't be able to deal with things like Obj-C/Swift interop which iOS developers were already jumping onto. And Microsoft's Windows 8 mobile initiative was pretty clearly a flop by this point.
Frankly, this Obj-C effort needed to be done way earlier, starting with AppKit, like back when Microsoft was panicking that OS X 10.4 Tiger was going to kick Longhorn's butt. If these tools had already been proven useful before the dawn of the iPhone, Microsoft might have had a chance of riding the iOS wave.
There seem to be bunch of DLLs in iTunes and Safari with familiar names.
Would have been good if someone made bindings for them, it would have been interesting to see what MacOS like stuff could work there, even if it just python bindings.
Oh, they've got a well-structured roadmap with milestones. Surely, this is will be a long-lasting bridge. And last commit was 3 years ago. And "This repository was archived by the owner on May 28, 2025. It is now read-only."
It's dead but still around. This is the stuff ripe for Jia Tan v4.0 to revive and backdoor.
11 comments
[ 4.6 ms ] story [ 31.4 ms ] threadFrankly, this Obj-C effort needed to be done way earlier, starting with AppKit, like back when Microsoft was panicking that OS X 10.4 Tiger was going to kick Longhorn's butt. If these tools had already been proven useful before the dawn of the iPhone, Microsoft might have had a chance of riding the iOS wave.
Would have been good if someone made bindings for them, it would have been interesting to see what MacOS like stuff could work there, even if it just python bindings.
I do not understand why Microsoft stopped this effort.
Paired with Win32 is easier than C++.
It's dead but still around. This is the stuff ripe for Jia Tan v4.0 to revive and backdoor.