3 ms·

Been a while since I did UI work but what happened to xaml/silverlight/wpf? I had the easiest time with with some complicated UIs when .Net came out with that

• oaiey 3y ago
  Well ... XAML and friends did not fly into the web. That is what happened. And the reason why the web feels clumsy, is because HTML is a document object model (for a floating and not paged document) and not a UI toolkit. And that will not really change. HTML made some moves to improve (like the flex display model) but still has not reached some of the core attributes of the WinForms or WPF layout models.
  • rizky05 3y ago
    [dead]
  • colejohnson66 3y ago
    > HTML made some moves to improve (like the flex display model)... Except that was CSS, not HTML. HTML is still just a representation of the DOM. Even the attempt at "semantic" elements (<section>, <article>, etc.) has basically failed, and been relegated to ARIA attributes. The "web" has settled on the trifecta of HTML for markup, CSS for layout, and JS for interactivity.
• colejohnson66 3y ago
  WPF was left to wither about the time .NET Core came out. In typical Microsoft fashion, they "deprecated without deprecating" it. They instead worked on the successor, MAUI, but were beaten to the punch by Avalonia. MAUI also took a "mobile-first" approach; There's tons of documentation about making mobile apps for it, but not as much for desktop apps. It's like they're trying to upset React Native. Avalonia, instead, focused on desktop apps, and seems to have won out in that space.