Microsoft wants to unify UWP and Win32 with Project Reunion
Microsoft's virtual Build 2020 conference started today and one of the major announcements that Microsoft made today unveiled Project Reunion officially.
Project Reunion is Microsoft's attempt at bringing Win32 programs and UWP applications together. The company hopes that Project Reunion will make it easier for developers to build applications for Windows and that it closes the gap that it created years ago when it focused on UWP.
Existing APIs, Win32 and UWP, will be unified and decoupled from the operating system according to Microsoft via tools such as NuGet.
When Microsoft launched Windows 10, it had big plans for Universal Windows Platform, its applications, and the Windows Store. The demise of Windows Phone and the reluctance of users and organizations to create and use Windows Store applications, resulted in a change in strategy.
Most developers continued to focus on Win32 programs while only a few created specific Store versions of their applications and even fewer new applications that were not available in one form or another as desktop programs.
Microsoft makes available all APIs to developers, regardless of whether they develop Win32 or UWP applications. Developers, especially those developing Win32 programs, may utilize newer APIs that Microsoft created specifically for the UWP platform to integrate the "latest functionality" in the programs.
For the past couple of years, we have been breaking down the barrier between Win32 (also called the Windows API) and Universal Windows Platform (UWP) APIs. Project Reunion expands this effort to make it easier to build a great Windows app. It will unify access to existing Win32 and UWP APIs and make them available decoupled from the OS, via tools like NuGet. This will provide a common platform for new apps. Plus, it will help you update and modernize your existing apps with the latest functionality, whether they’re C++, .NET (including WPF, Windows Forms, and UWP) or React Native. As we decouple existing APIs and add new APIs, we are also doing the work to polyfill, as needed, so the APIs work down-level across supported versions of Windows.
The first two components that Microsoft revealed as part of Project Reunion are WinUI 3 Preview 1 and WebView 2. The former is a "high performant, Fluent-optimized native UI framework for Windows" according to Microsoft that developers may use to create programs that adapt and scale across all sorts of devices. WebView 2 enables developers to integrate web content using the rendering engine of the new Microsoft Edge and Chromium into their Windows applications.
Closing Words
Microsoft is making available UWP specific APIs to developers who don't develop for the platform. One of the major strengths of the Windows platform is the programs that are available for it. The vast majority of these are not UWP applications and the exclusion of these from newer developments and features was a mistake from the get-go in my opinion.
It remains to be seen how this will turn out in the long run.
Now You: What is your take on the development?
Reminds me of better times when programs where called programs and apps didn’t exist. Now dekstop users have to deal with mobile-centric user interfaces.
I loved programming as a kid. I read assembly on the Amiga like other people read the newspaper. And then on the PC. But then came the notion of “object oriented programming”, and all the fun was suddenly gone. Even after 30 years I cannot get a grasp on what OOP is, and the moment I hear the word “method” I get angry and nervous. Looks like it’s an abstraction beyond my comprehension, because I find that’s not the way how a computer works. M$ has messed it all up. Sad.
WinUI seems to be geared towards makings applications with UWP style user interfaces. Nobody wants tablet style interfaces on their desktop, so this seems doomed to fail again.
Furthermore, it’s now impossible to have any confidence in any of Microsoft’s APIs. They’ve been in full headless chicken mode for some time, going from one thing to the next without any plan. No sane developer is going to commit their time to learning another API, only for it to fail again.
It’s going to be very hard for Microsoft to regain developer’s confidence, and they’ve got themselves into such a mess with all their different APIs that I honestly don’t know what they can do. Personally, I’ve given up on Microsoft entirely and I’m now using Qt for all my personal projects. It would take a minor miracle for me to even consider learning another Microsoft API.
UWP is horrible. I don’t want touch screen apps on my desktop computer.
Yes, me too. No use of these apps on Desktop PC.
An admission that UWP has failed and perhaps a step in the right direction; yet I fear that MS will manage to bring all the issues of UWP to the traditional applications. Not now, not next year, but eventually.
What a colossal waste of time, money and resources. All of which could have been spent on making Windows 10 better and less buggy.
Actually, the more MS does *not* focus on any of its products, the better it is. They regard making something worse as “improvement”.
The less UWP in my OS the better. I’ll keep using LTSC, tyvm.
I am currently forced to endure the regular Windows 10.
What would be the least painful way of acquiring Windows 10 LTSC for testing purposes?
Thanks in advance.
Windows 10 Enterprise 2019 LTSC (x64) – DVD (English)
File Name: SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_MLF_X21-96425.ISO
Languages: English
SHA1: D5B2F95E3DD658517FE7C14DF4F36DE633CA4845
Windows 10 Enterprise 2019 LTSC (x86) – DVD (English)
File Name: SW_DVD5_WIN_ENT_LTSC_2019_32-bit_English_MLF_X21-96424.ISO
Languages: English
SHA1: 220EB673D4AED9F1652C1CE3D2731CD96A8138F2