I have never liked the habit of using code to describe a user interface. Declarative XML works and the history is blunt about it. HTML proved it. XAML proved it. Every attempt to replace that pattern since the late 1990's, even the VRML era I worked through, keeps falling short of what XAML already solves.
This looks promising and I want to see where it goes next.
Thanks to @jezell for the pointer and credit to @wieslawsoltes for the work.
Tell me if I am misremembering, but were not some of the former XAML engineers from Microsoft involved in the early days of Flutter as well?
@Microsoft let me get this straight: if i want to upgrade to .NET 10 in November, i'll be forced to run VS 2026? A release you havent even publicly anounced until a week ago? So the VS 2022 licenses i just spent money on are basically worthless?
Windows is actually evolving into a miserable, bloated, and inconsistent operating system, with its only reason for existence now being to retain subscribers to Microsoft services.
Companies should allow WFH in cities like Bangalore and Mumbai. If physical presence isn’t needed, there’s no point wasting time, energy, and money battling traffic and poor infrastructure. Half your energy is wasted just reaching office.
@DevLeaderCa Never stopped writing them. I'm actually writing them to connect to internal apis so our support staff doesn't have to use the webapps. So much better responsiveness.