Linked by Thom Holwerda on Thu 26th Jan 2012 15:13 UTC
Mac OS X "It's no longer possible to write a single app that takes advantage of the full range of Mac OS X features. Some APIs only work inside the Mac App Store. Others only work outside it. Presumably, this gap will widen as more new features are App Store-exclusive, while sandboxing places greater restrictions on what App Store apps are allowed to do." Anybody surprised by this, here's the clue stick. Please proceed to hit yourself with it.
Permalink for comment 504811
To read all comments associated with this story, please click here.
RE[3]: No MacOS X for me.
by kaiwai on Fri 27th Jan 2012 02:42 UTC in reply to "RE[2]: No MacOS X for me."
Member since:

Microsoft is cleaning up their act with the new WinRT APIs in Win8. Metro apps will only have limited access to legacy APIs, only the safe ones. No matter how Metro apps are written - native, .NET, Silverlight, HTML/JS - they will all use the same WinRT code, perhaps with idiomatic wrapper APIs but the same code.

I haven't heard one way or the other whether Win8 desktop apps can use WinRT yet, as the non-UI APIs should apply to desktop apps too. That would be nice to see, and a desktop-usable subset of WinRT might be portable to Win7 as well.

Metro is just surface stuff. The big change is WinRT.

Microsoft touted WinRT as a 'native subsystem' in its own right since it was launched it has since my shown that this so-called 'native subsystem' is in actual fact little more than a shim sitting on top of win32 given the number of WinRT frameworks that are still referencing back to GDI for starters (haven't Microsoft heard of their own in house built API's known as DirectWrite/Direct2D?).

Then there is the issue of the desktop - the desktop isn't going anywhere but when are Microsoft going to provide a native alternative to the 30 year old common control and dialogues that are sitting on top of old legacy API's such as GDI? it has been almost 5 years and Microsoft still has no road map to move away from the old and move to the new.

Lets get one thing straight, I am not expecting them to throw away backwards compatibility but what do expect at the very least is for Windows to have a clear line drawn in the sand between what is legacy and what is the future (so developers know what parts of their own software stack need to be moved over to the new API's) and more importantly for all the built in applications of Windows to be moved over to the new API's. Sure, have common control and dialogues dll's for backwards compatibility but there is no reason why explorer.exe shouldn't be making a single reference to these legacy API's nor should there be a reason for internet explorer to make any reference or Windows Media Player etc. etc.

It is time that Microsoft got its act together because so far to me it appears that everything they've done so far is half assed and half baked - a friday job where the absolutely minimal amount of works is done in a hope that no one will noticed the rotting piles underneath the whole edifice.

Reply Parent Score: 3