Quote:
Originally Posted by maximus83
This is not correct IMO. Windows 8 is much more than just an eye candy type of front end. Users may or may not like the new UI, but there IS a lot of new substance under the hood. If you look at the publicly released information about it (see this article, that shows the architecture), includes a new fundamental runtime layer called "WinRT." There are various new UI-layer development options, but under the hood, the WinRT layer is a completely new, OO way of doing things (as opposed to the old-school calling of Win32 layer). To quote this article: "WinRT isn’t another abstraction layer; it resides directly on top of the kernel just like the Win32 API. This marks the first major break in the core of Windows since Win32 was introduced in 1993 with Windows NT. WinRT represents a new application execution environment with semantics that are very different than Win32."
And this article makes a similar point:
"WinRT (the new Windows Run Time) is not a replacement for Silverlight or .NET, it's a replacement for Win32. And that means that it's the new native runtime for Windows, and not a managed code layer that sits higher on the stack." |
But I can still run pretty much any app that works on Windows 3.1 beyond on Windows 8, which is my point. They needed to completely ditch the backwards compatibility which makes Windows prone to security issues in the first place. The fact that Windows Mobile and Windows Phone use Windows Embedded instead of just Windows makes them much more secured.
WinRT will be ditching that old framework, but the versions that run on Intel won't.