Windows Runtime - The New API

[TI-994A]

I'm sure that you've heard about the new Windows Runtime API in Windows 8, which has to be used in order to write Metro apps. Since this entails using the COM-based functions from this new API, and limited use of Win32-API functions, what's GLBasic's game plan for Windows 8 compatibility?

[Kitty Hello]

I have not checked the details, yet.

[MrTAToad]

GLBasic works fine on Windows 8 desktop - all programs revert to using the standard Windows layout when you run a program.

Don't know about Windows On ARM though - that could probably mean a new set of libraries and what not..

[TI-994A]

GLBasic works fine on Windows 8 desktop - all programs revert to using the standard Windows layout when you run a program.

Don't know about Windows On ARM though - that could probably mean a new set of libraries and what not..

Yes, but technically that would be running on "compatibility mode", because Windows 8 is Metro based, which is built upon the Windows Runtime. Taking a cue from Apple's App Store, Metro apps can only be sold through the Windows Store, and will otherwise not install on any device. The store will not sell non-Metro apps, but they may be showcased in the Windows Compatibility Center and listed in the store if they are Windows Desktop App Certified.

This is the new core API for both the Intel (WOI) and Arm (WOA) platforms; only on handheld devices it's called Windows RT, and Metro based code is supposed to be fully portable across these platforms.

Windows 8 actually has two separate APIs, sitting side by side; and logic tells us that one of it will have to go (eventually). Guess which one is more profitable for Microsoft?

[Kitty Hello]

If they break backward compatibility, noone will get a new windows. That's why win is the best platform. It runs any windows program ever made ( ok x64 dropped win 16 bit support, but hey)

[MrTAToad]

Certainly be able to save some money if only Metro applications are allowed in the store!

[TI-994A]

If they break backward compatibility, noone will get a new windows. That's why win is the best platform. It runs any windows program ever made ( ok x64 dropped win 16 bit support, but hey)

Hi Gernot. You're right, Windows has always had very strong legacy support; even DOS apps still work today. I'm sure (I hope) that it'll be a while before we actually have to worry about this. But once this new paradigm goes mainstream, there will be no real backward compatibility. The Windows Runtime is a totally different beast from the twenty-five-year old WinAPI; to maintain legacy support will actually involve maintaining two different and separate OS cores. If they do decide to support it, we'd probably be looking at some sort of virtual machine, like they did for DOS and the Win16-API with the NTVDM.

The current WinAPI app base may be quite formidable, but Microsoft is not getting a single cent from that; the 30% incentive will definitely be a huge motivator for them to push this new "jailed" Windows Runtime as the de facto environment, and drop the current WinAPI without a second thought. They know that people are generally adverse to change, and if given the choice, their new cash cow may not float.

While the good news is that the new API favours C++, the old WinAPI-dependent libraries may not comply.

[Kitty Hello]

Think of all the big companies that would have to totally rewrite their apps. It's totally impossible.

[spicypixel]

I don't fully understand all of what you're saying but my general impression is that of a new Microsoft OS which effectively isn't Windows compatible. The worry of backward compatibility is not a problem. To adopt a more layman style approach I have a ZX Spectrum and lots of software blah blah blah, Commodore buy Sinclair and release a new ZX Spectrum 64 (lets say) which is a new machine not compatible with the original ZX Spectrum.

Oh no my software won't work anymore, major financial crisis everywhere..... errr call me foolish but why not use both machines. Tada! lol.

[backslider]

Windows 8 Metro won't have backward compatibility but it will have a optional Windows 7 like user interface where you can run all old (Windows 7!) applications.

[TI-994A]

Windows 8 Metro won't have backward compatibility but it will have a optional Windows 7 like user interface where you can run all old (Windows 7!) applications.

Yes, and that's called compatibility mode; and we should survive on that for quite some time. But although we can emulate the Metro style UI, we won't be able to utilise the Metro-centric functionalities, like background mode, Start Screen notifications, etc. We'll be legacy apps.

[DaCarSoft]

This kind of industry movements makes me love more and more virtualization...

Micro$oft will die in short time if they break its backward compatibility...

[erico]

Micro$oft will die in short time if they break its backward compatibility...

I agree, and worse for them is that today we have plenty more alternatives, so such a move will get big companies to spend a lot of cash, they might as well spend this cash moving to a time-reliable platform.

[MrTAToad]

I presume there are no plans at the moment to update the Windows executable so that it is Metro compliant (and thus can be sold in the Marketplace) ?

[erico]

yep, that would precisely be the point I guess.