3 ms·

This is true, but it allows them to test the waters. If it is successful, it further opens the door to web-style programming on windows. And as MS keeps swit

This is true, but it allows them to test the waters. If it is successful, it further opens the door to web-style programming on windows. And as MS keeps switching their UI story, having react to force them on an externally dictated standard might finally mean, well, a default UI default framework on windows again. Something we've been missing since Win32 ruled the earth.

dahpu 5y ago
Going from the oldest UI elements Win11 currently has, IIRC it something from Win2k, all the way up to React Native, Windows is becoming a living museum of UI.
- quyleanh 5y ago
  Lol. Sad but true. It's hard to unify all the inconsistency, since the tech changes by day.
  - dahpu 5y ago
    It is hard, but Microsoft has the workforce and knowledge to do it. Yet they are not comitted to it, one reason being compatibility. There are businesses today relying on 10+ year old custom solutions developed for XP.
WorldMaker 5y ago
This React Native work is using the same "default UI framework" from Windows 8 (WinUI/WinRT, whatever you want to call it), the big thing that has shifted was Windows 8 did JS bindings directly inside IE11 and "Spartan" Edge and now the preferred tool seems to React Native when working with JS (or TS). (Which in some ways is actually a regression from the Windows 8 approach because the IE11/"Spartan" Edge-backed plan supported WinRT bindings and WinUI user interfaces "progressively" in PWAs: rather than recompiling your JS for React Native with its own React Native "skin" there was a more direct path to "upgrade" a regular web-hosted app and boring "old fashioned" HTML DOM to WinRT/WinUI. Somewhat ironically, too, the WinUI name even came from these earlier Windows 8 efforts, but WinUI.js died as Microsoft decoupled WinRT bindings from IE11/"Spartan" Edge and never got a "3.0".) I think the narrative that Microsoft keeps switching their UI story is more about the confusion of the shifting bindings than actually about the stack as whole. The stack is relatively consistent over time, just things like .NET versions kept changing (and where .NET fits with respect to the application hosting model/lifecycle) and JS saw this regression from being a "first class" supported binding with a path for PWAs to it's finally back in React Native (and currently only React Native), and even is starting to feel "first class" again, if you don't mind React Native now as the only way forward.

dahpu 5y ago

Going from the oldest UI elements Win11 currently has, IIRC it something from Win2k, all the way up to React Native, Windows is becoming a living museum of UI.

quyleanh 5y ago
Lol. Sad but true. It's hard to unify all the inconsistency, since the tech changes by day.
- dahpu 5y ago
  It is hard, but Microsoft has the workforce and knowledge to do it. Yet they are not comitted to it, one reason being compatibility. There are businesses today relying on 10+ year old custom solutions developed for XP.

WorldMaker 5y ago

This React Native work is using the same "default UI framework" from Windows 8 (WinUI/WinRT, whatever you want to call it), the big thing that has shifted was Windows 8 did JS bindings directly inside IE11 and "Spartan" Edge and now the preferred tool seems to React Native when working with JS (or TS). (Which in some ways is actually a regression from the Windows 8 approach because the IE11/"Spartan" Edge-backed plan supported WinRT bindings and WinUI user interfaces "progressively" in PWAs: rather than recompiling your JS for React Native with its own React Native "skin" there was a more direct path to "upgrade" a regular web-hosted app and boring "old fashioned" HTML DOM to WinRT/WinUI. Somewhat ironically, too, the WinUI name even came from these earlier Windows 8 efforts, but WinUI.js died as Microsoft decoupled WinRT bindings from IE11/"Spartan" Edge and never got a "3.0".) I think the narrative that Microsoft keeps switching their UI story is more about the confusion of the shifting bindings than actually about the stack as whole. The stack is relatively consistent over time, just things like .NET versions kept changing (and where .NET fits with respect to the application hosting model/lifecycle) and JS saw this regression from being a "first class" supported binding with a path for PWAs to it's finally back in React Native (and currently only React Native), and even is starting to feel "first class" again, if you don't mind React Native now as the only way forward.