Re:MS to Give Windows 10 a ‘Modern’ Overhaul with Light Weig...
by Santosh83 on Monday January 29, 2018 @11:42AM
(#16258532)
Win32 is not completely legacy. Parts of the API have continued evolving and I don't see insurmountable technical limitations to it evolving further, except that MS prefers a fresh sub-system. The parts that were truly legacy like Win16 or MS-DOS or virtual 8086 have all been already removed.
[ Parent
| on HN ]
Re:MS to Give Windows 10 a ‘Modern’ Overhaul with Light Weig...
by contextfree on Monday January 29, 2018 @11:55AM
(#16258641)
USER/GDI haven't been removed, which is a big problem as they make proper UI and application isolation impossible. Removing this dependency is one of the major goals of WinRT/UWP/OneCore effort.
Re:MS to Give Windows 10 a ‘Modern’ Overhaul with Light Weig...
by garganzol on Monday January 29, 2018 @11:59AM
(#16258688)
What is the end goal? A headless /dev/null? (pardon my exaggeration). As far as I can see, this direction won't attract a lot of customers. People want the simplicity of usage (and it does not necessarily means simplicity of underlying implementation).
Re:MS to Give Windows 10 a ‘Modern’ Overhaul with Light Weig...
by pjc50 on Monday January 29, 2018 @12:15PM
(#16258867)
App-to-app isolation is probably necessary in the end; at the moment a win32 app can just PostMessage() gaily into any other app whether it likes it or not.
That doesn't necessarily mean getting rid of the old API, but it might mean radically sandboxing it.
Re:MS to Give Windows 10 a ‘Modern’ Overhaul with Light Weig...
by garganzol on Monday January 29, 2018 @12:23PM
(#16258940)
A good point. But this is mostly a solved problem. App can only PostMessage to another app running under the same user account. Regarding app sandboxing: it sounds good on paper, but in reality it becomes evident that sandboxing breaks interoperability between the apps returning all of us to the stone age of computing circa 197x.