"...Microsoft is using React Native for Windows to deliver the Your Microsoft Account page in Windows 11 Settings." (Because they want to expose natively styled website functionality through the app.)
I was worried. Not that I like the ridiculous Windows 10 Settings app, but I do like UWP+Xamarin.
Microsoft's internal civil war over the presentation layer has been going on for what seems like a decade and pretty much has only managed to destroy Microsoft as purveyor of visualization rather than find a winner internally.
As someone who has been developing in React Native for the past 3 years: please don't. Debugging on RN is ridiculously bad and sometimes you get completely unrelated errors, not to mention the horrible memory usage.
7 comments
[ 4.4 ms ] story [ 20.1 ms ] threadI was worried. Not that I like the ridiculous Windows 10 Settings app, but I do like UWP+Xamarin.
I used to heavily advocate for .NET Native and C++/CX with WinRT, as for me that is what .NET 1.0 should have been all along.
Nowadays I just can't, just keep using Win32 and Forms/WPF until the civil war comes to an end.
I recently discovered that the Visual Studio installer is using Electron.
For all the criticism of Apple regarding backwards compatibility they have a clear story on the UI for macOS. Cocoa -> SwiftUI.
The backslash was big enough that they rewrote it back into WPF.
There is a tweet from the team about it, and you can validate yourself by running the latest installer versions.
Regarding Apple, no they don't, you are missing Catalyst, and the mess about what which OS features does each of them support.
There is one ATP podcast episode where they go on a side rant regarding their state.