Linked by Thom Holwerda on Tue 6th Mar 2012 23:27 UTC
Windows As you may have seen, David's been taking care of OSNews for a few days because I'm quite busy with work. Still, there's one thing I'd like to talk about: the desktop mode in Windows 8. I wish I could've added this to the first impressions article, but I only arrived at this conclusion yesterday: desktop mode in Windows 8 is Microsoft's equivalent of Mac OS X's Classic mode.
Thread beginning with comment 509882
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: The difference is...
by malxau on Wed 7th Mar 2012 23:44 UTC in reply to "RE[3]: The difference is..."
malxau
Member since:
2005-12-04

I am not a desktop developer, but I use ASP.NET and PHP on IIS ... Thanks though for clearing that up.


I think this makes my point nicely.

IIS isn't able to run in Metro. It can't - the environment is different, and IIS doesn't want to find itself killed or suspended randomly. The class of applications you're writing are permanently scoped to the non-Metro world, with no path into it.

So let's hope the "legacy" desktop isn't pure legacy, lest this (and all other server-side code) wouldn't be feasible to run on Windows. This is very different to OS 9 -> OS X where server code could be migrated, and native server code worked much better on OS X than it ever did on OS 9 due to the improved platform functionality. In time OS 9 could be removed wholesale. That's just not what's happening here.

Reply Parent Score: 2

lucas_maximus Member since:
2009-08-18

What nonsense are you talking about?

IIS runs a service and has nothing to do with Metro.

HTML 5 and JS apps run using whats sounds like Trident, C# and VB apps can be used with XAML can use the same APIs as C++ apps.

Edited 2012-03-08 12:25 UTC

Reply Parent Score: 2

RE[6]: The difference is...
by malxau on Thu 8th Mar 2012 12:50 in reply to "RE[5]: The difference is..."
malxau Member since:
2005-12-04

What nonsense are you talking about? IIS runs a service and has nothing to do with Metro.


There are many things that are interrelated here. Metro is a UI. WinRT is an API for Metro. The Desktop is a UI, and Win32 is an API for the Desktop. IIS uses Win32, even though it runs as a service. Although it exposes no direct UI, it exists in a desktop world by virtue of the API it is using, and the environment that the API lives in prevents it moving to an alternate API.

My original post was trying to point out that the API difference here is the key part. The WinRT API just doesn't support the kind of things Win32 does. It doesn't support things like services. It doesn't support long lived multitasking things. It doesn't support common IPC mechanisms. The kind of things IIS needs are absent. It is not a successor technology, it is a parallel universe with heavy restrictions. For everything that can't live with those restrictions, Win32 (and all of the layers that eventually call it) is the only game in town. This is very different to OS 9/OS X, where OS 9 technologies had an equivalent on OS X, and a decent abstraction layer to make porting possible.

Reply Parent Score: 2