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.
Thread beginning with comment 504859
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: No MacOS X for me.
by moondevil on Fri 27th Jan 2012 09:31 UTC in reply to "RE[3]: No MacOS X for me."
moondevil
Member since:
2005-07-08

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?).


This only shows how little you know about WinRT.

WinRT is a new Windows personality, as OS/2, Posix and Win32 are. As such it is built on top of ntdll.dll.

The DirectX APIs are also COM based anyway, and have been recoded for WinRT. The WinRT DirectX is not 100% like the Win32 WinRT.

Since Direct2D, GDI is considered legacy and might be gone in future releases.

Reply Parent Score: 2

RE[5]: No MacOS X for me.
by kaiwai on Fri 27th Jan 2012 14:00 in reply to "RE[4]: No MacOS X for me."
kaiwai Member since:
2005-07-06

This only shows how little you know about WinRT.

WinRT is a new Windows personality, as OS/2, Posix and Win32 are. As such it is built on top of ntdll.dll.


If it is a 'Windows personality in its own right' then how do you explain the dependencies linking back to Win32 API's such as GDI? if it were a clean break from the past then shouldn't you see WinRT making calls to Direct2D/DirectWrite instead of GDI? Either it is a subsystem in its own right that is implemented in a pretty half baked fashion or it is merely a shim - either way the end result is the same, they haven't made a break from the past because either way WinRT is still dependent on win32 or at least parts of it.

The DirectX APIs are also COM based anyway, and have been recoded for WinRT. The WinRT DirectX is not 100% like the Win32 WinRT.

Since Direct2D, GDI is considered legacy and might be gone in future releases.


Which means very little given that one expects these sorts of things announced by Microsoft themselves rather than speculation by those if us in the enthusiast community.

Edited 2012-01-27 14:03 UTC

Reply Parent Score: 2

RE[6]: No MacOS X for me.
by Thom_Holwerda on Fri 27th Jan 2012 14:20 in reply to "RE[5]: No MacOS X for me."
Thom_Holwerda Member since:
2005-06-29

they haven't made a break from the past because either way WinRT is still dependent on win32 or at least parts of it.


They kept the parts around that made sense - or are you arguing Mac OS X wasn't a clean break because it still kept things like QuickTime, Desk Accessories, and more, from the MacOS days aound?

Reply Parent Score: 1