The entire point of Uno is being an implementation of UWP (notice the very specific goal here), while using native UWP with no overhead when on Windows.

Since WinUI 3 is multiplatform (in conjunction with the first party Linux/Android and OSX/iOS support in .Net 5 and 6, and with MAUI), Uno no longer needs to exist outside of dealing with legacy UWP code (which, as per Microsoft rules, shall never die).

Also, re: web UIs, I hate to inform you, but everyone hates these. They are slow, clunky, optimized for all the wrong things, inconsistent, and sometimes ugly. The move to HTML canvas-based UIs in otherwise native apps Android and iOS is why most apps on phones are slow, even though a purely native one would have been fast on an ancient phone. Please do not repeat this mistake.

> Since WinUI 3 is multiplatform

Hm? I thought MAUI was the multiplatform UI toolkit and WinUI 3 was the native Windows 10 UI toolkit (evolved from UWP) repackaged for bundling with each app?

Multi-Platform in the windows division means Xbox, older win 10 versions and things. Microsoft uses this term very naive.

I hope I do not destroy the dreams of someone.

> I hope I do not destroy the dreams of someone.

You kinda did. :)

I was trying to grok the point of Uno if WinUI was truly multi-platform in the MacOS/Linux/Android/iOS sense.

Just like for Apple multiple platform means macOS, iOS and watchOS, because at the end of the day it isn't the same OS, nor hardware.

If you are building form apps and stuff where delivering something working is the main objective (most enterprise apps) web UI is by far the best choice - ecosystem is huge, plenty of developers and designers to hire, tools let you export stuff like styles directly from designs, etc.

If you care about user experience - writing it for each platform would have ended up being faster in the last app I did with flutter - so many subtle things that dragged the development out for weeks where as native had all these things working out of the box. I haven't worked with Xamarin in a while but I remember the quality was the worst out of all solutions I've used. So many moving parts, "this works in the latest version" and then half of other dependencies haven't been updated, and you just said the same thing.

Yes, but Flutter uses a strange little JS dialect nobody wants to learn. Were both created due to the way Google gives out bonuses and promotions?

I dont' think that really matters. If Flutter solves the cross platform issue, people will deal with Dart. And if Flutter sucks, nobody will put up with it sucking just because they love Dart. Either way Dart isn't the big picture, Flutter is.

I disagree. I would not recommend flutter to anybody precisely because of how bad Dart is. It's such a productivity/maintenance drag that the framework is not worth it.

Dart is much more similar to C# than JavaScript

It's the worst of all worlds TBH. It has terrible reflection and metaprogramming capabilities which leads to ridiculous solutions like code generators at every step. Type system is super weak (eg. it just gives up on type checking ternariea for eg., had multiple runtime type errors because dart couldn't catch it at compile time), but at the same time also closed and very inflexible. Working with immutable types is ridiculously bad compared to C# or JS. Serialisation is terrible as well.

Flutter would have been a much better framework if it was built on typescript