Read on Twitter
Thread (see also: why sandboxing is ππππΉ) https://twitter.com/SwiftOnSecurity/status/974408573013852166
Can we talk about Project Reunion for a moment?
Cool. Let's begin. (thread) https://twitter.com/SwiftOnSecurity/status/1014727313043415040?s=20
Cool. Let's begin. (thread) https://twitter.com/SwiftOnSecurity/status/1014727313043415040?s=20
Let me preface this by saying that Project Reunion is a good thing. Between .NET 5, the changes to WinRT, and WinUI 3, it's poised to become THE way to make Windows Apps
But it was born out of necessity, because developers are just as (if not more) stuck in their ways than users
But it was born out of necessity, because developers are just as (if not more) stuck in their ways than users
When Microsoft introduced WinRT, the UWP XAML framework, and the Windows store, it had two sides:
One side loved it. It was modern, it was convenient, and it was πππΈπππ.
Another side hated it. It was restrictive and slower in some ways, and above all, it was too different
One side loved it. It was modern, it was convenient, and it was πππΈπππ.
Another side hated it. It was restrictive and slower in some ways, and above all, it was too different
For a very long time, making a native "Windows App" was like a light switch. You either used:
WPF / WinForms, which was flexible and familiar.
or UWP, which was convenient and secure by design.
There was no in between. You used one or the other.
WPF / WinForms, which was flexible and familiar.
or UWP, which was convenient and secure by design.
There was no in between. You used one or the other.
Project Reunion takes that black or white and turns it into a gradient.
Classic desktop apps can a la carte into all the newer UWP features, and slowly upgrade over time.
UWP apps can escape the sandbox entirely (if they want to run ONLY on Desktop)
Classic desktop apps can a la carte into all the newer UWP features, and slowly upgrade over time.
UWP apps can escape the sandbox entirely (if they want to run ONLY on Desktop)
Microsoft aims to slowly turn all WPF / WinForms apps into UWP by letting them use UWP's core technologies, which is fantastic for everyone.
Except UWP apps are now allowed to use older APIs which were κ±α΄α΄α΄α΄κ±α΄α΄ to be obsolete one day.
Except UWP apps are now allowed to use older APIs which were κ±α΄α΄α΄α΄κ±α΄α΄ to be obsolete one day.
Windows 8 / Windows 10 have been a nearly decade long effort to unfuck the Windows ecosystem.
Let me quote this again, but now with the above in mind: https://twitter.com/SwiftOnSecurity/status/1014727313043415040?s=20
Let me quote this again, but now with the above in mind: https://twitter.com/SwiftOnSecurity/status/1014727313043415040?s=20
This is my only problem with Project Reunion, but I don't blame Microsoft for what they did.
Developers screamed for years. "It's too restrictive", "Why can't I do X", "but I've always done Y", "Z was better"
Developers screamed for years. "It's too restrictive", "Why can't I do X", "but I've always done Y", "Z was better"
UWP was created to benefit users, but it didn't make devs happy.
Project Reunion was created to make developers happy, but it won't benefit users or sysadmins.
Project Reunion was created to make developers happy, but it won't benefit users or sysadmins.
Project Reunion is a compromise, not a permanent solution.
But it is the road TO a permanent solution. Fingers crossed that Microsoft can tread the right path
But it is the road TO a permanent solution. Fingers crossed that Microsoft can tread the right path
