3 ms·

My impression is that MAUI was released with a lot of fanfare but wasn't really ready (but that's just from articles I read, I haven't tried it myself). That's

My impression is that MAUI was released with a lot of fanfare but wasn't really ready (but that's just from articles I read, I haven't tried it myself). That's before even getting into lack of official Linux support. It then seems to have very little attention. It fits the classic Microsoft pattern of releasing a developer technology that doesn't quite work, then abandoning it before they ever finish it. For example, WinForms was meant to get hardware acceleration but, before then, was soft-deprecated in favour of WPF. It seems like that isn't your experience, is that right? I'm genuinely curious because I want to like MAUI – I'd love a cross platform (Windows, Mac, Linux), hardware accelerated, C# GUI toolkit (that works and is supported).

spinningslate 3y ago
> My impression is that MAUI was released with a lot of fanfare but wasn't really ready [...] >It fits the classic Microsoft pattern of releasing a developer technology that doesn't quite work, then abandoning it before they ever finish it. My sense is that MS is all-in on "web ui" (html/css/[js|ts]). Native apps don't fit with the commercial imperative to get as much compute happening in Azure as possible. The Windows desktop increasingly has just one purpose: to maximise the likelihood that the end consumer will use Microsoft's cloud, and not someone else's. The Desktop UI is now a bedraggled mix of several UI toolkit generations, with many built-in apps going all the way back to the original Win API. Microsoft's own headline apps - Office and Teams - have a web tech future. Teams started there, Office is going through a long, slow and somewhat painful migration. Windows is slowly becoming just a remote desktop. You don't need native apps on those.