4 ms·
In that light, it is troubling that Friday’s blog post [0] announced “moving core Windows experiences to the WinUI3 framework” as a measure to improve the quali
by layer8 7mo ago
In that light, it is troubling that Friday’s blog post [0] announced
“moving core Windows experiences to the WinUI3 framework” as a measure to improve the quality of said experiences.
[0] https://blogs.windows.com/windows-insider/2026/03/20/our-commitment-to-windows-quality/ https://blogs.windows.com/windows-insider/2026/03/20/our-com...
- NetMageSCW 7mo agoThe only good thing to say about that is it removes the stupidity of using Electron (or the Microsoft Edge equivalent) for built-in Windows apps and the Start Menu. SMH.
- bigfatkitten 7mo agoWhoever was responsible for that should be fired.
- deleted 7mo ago[deleted]
- dminik 7mo agoThe start menu never was electron. It's react native desktop. So, nodejs creating and updating native (well, winui 3) controls.
- jcelerier 7mo agoHeh, nodejs uses V8 which shares legacy with WebKit's JavaScript core, itself being forked from KDE's KJS. Fun to think that eventually, some KDE code spiritually made its way to the windows start menu
- pjmlp 7mo agoAs long as it only applies to Microsoft employees, maybe the pain using C++/WinRT will finally improve the Visual Studio tooling for the rest of us, but I doubt it. Thus better leave WinUI to the Windows team.
- fodkodrasz 7mo agoThese steps are necessary stepping stones in getting the thing good, the question is, given Microsoft's tendency to abandon UI frameworks halfway, apart from the classical ones listed above, is if they will keep it focused until its gets as mature as those.