Jump to content
|Topic||Stats||Last action by|
|The Jimquisition: Warner Bother||
|Win7 Upgrade To Windows 10 TP||
|Cortana will also be your personal tech support in Windows 10||
|PlayStation Plus Instant Game Collection: May 2015||
Posted 04 September 2014 - 22:34
Posted 05 September 2014 - 21:01
Since Windows Vista, Microsoft has been separating different areas of Windows this has continued with Windows 7, Windows 8 along with their Server Line. Each area has grown isolated as in nowhere near as dependent on other parts of the OS. Do you think we could be headed to removal of the NT kernel (except for virtualization) and moving to a more developed version of Singularity which was developed by Microsoft Research?
More info on codeplex.com
Unfortunately, not as long as the backward-compatibility boat-anchor hangs around the neck of Windows as a platform.
For all too many developers (let alone users) backward-compatibility means all the way back to XP - resistance to anything that isn't backward-compatible to XP, and especially in enterprises, has gotten more and more vociferous.
Posted 05 September 2014 - 21:07
XP? I still occasionally play a few games from the 95 era
For all too many developers (let alone users) backward-compatibility means all the way back to XP
Posted 05 September 2014 - 21:08
Comments from the link:
Posted 05 September 2014 - 21:15
Last I heard they're still working on this, some small team is.
Posted 06 September 2014 - 10:55
Posted 06 September 2014 - 11:05
Microsoft is better off with an OS that works under .NET from a stability and security point of view. Unfortunately .NET still needs some work to perform as good as native (see .NET Native).
Microsoft can run more than one kernel on the same hardware (see XB1). What if you had the managed kernel and the native windows kernel side by side? Say switch between them when you run a native app?
I suspect even Microsoft Office will be managed code soon.
Posted 06 September 2014 - 13:53
Posted 06 September 2014 - 15:34
To the OP - How do you mean (NT kernel (except for virtualization) ) As in the NT Kernel would only be virtualized?
Posted 07 September 2014 - 23:04
When we're talking about something like a kernel, the only thing .NET would really offer is memory safety, you don't have the sandbox or anything like normal apps.
And what would be the benefit of running different kernels for different apps? (Calling into native code from managed code is fast, it's the opposite that's slower)
That is not true, code safety is very high in .NET.
The two kernels will run in parallel not within each other. The benefit is a smooth transition from a messy windows implementation. Security became an issue shortly after Windows XP came out and there is a lot of code to refactor for maintainability, security and modularity.
Posted 07 September 2014 - 23:23