3 ms·
They would have to do some sort of virtualization since there's literally no restrictions on what APIs you can access. There's so much cruft and invalid paradi
by cptskippy 7y ago
They would have to do some sort of virtualization since there's literally no restrictions on what APIs you can access. There's so much cruft and invalid paradigms in the old APIs it makes sense to roll new ones.
I think the approach they're taking to refactoring the Control Panel into the Settings App is smart. They're dog-fooding the Frameworks they're expecting others to use, slowly migrating functionality that's relevant to a modern Windows platform, and keeping existing functionality around until they've replicated it.
I also like that the apps are responsive. I use the snap feature a lot and it's nice that the Apps will adapt to the dimensions I relegate them to.
- uxp 7y agoI'm a .NET developer and I can't tell you how many times I've searched for documentation and come across something that's targeting UWP which is different than WPF and entirely not the same as WinForms and it takes way too much energy trying to identify why exactly the documentation isn't what you want. I thought Microsoft was more or less sunsetting WinForms until they also announced WinForms for .NET Core a couple months ago. https://docs.microsoft.com/en-us/dotnet/core/porting/winforms https://docs.microsoft.com/en-us/dotnet/core/porting/winform... I literally have no idea what Microsoft is doing anymore. Sometimes it feels like Linux was 10 years ago when I would accidentally install Konquerer on Gnome and all of a sudden I had two desktop systems installed and my root drive had doubled it's consumed harddrive space. It basically worked, but it was a terrible experience.