TL;DR:

* Uno is a vendor-led Windows/WinUI inspired and based UI platform that was originally concieved as a way to port modern Windows Apps to other platforms. Since then, it's evolved a lot of different capabilities and paradigms, but ultimately is basically cross-plat WinUI with extensions. * Avalonia is a OSS platform concieved as WPF with some of the warts removed, and cross platform. It uses a lookless theming and drawing primites instead of native APIs/Controls to render it's UI. * Maui is a .NET/Msft-blessed platform that is basically a rebranding of Xamarin.Forms with some improvements and renewed investment. It also largely uses native APIs/controls, and has a contruction style that is kind of a mix between WPF and WinForms.

Maui does not (at present) offer Linux support. There's a community effort, but AFIAK it hasn't gotten a lot of steam yet.

Recognizing that YARP's goal is to be, well, a reverse proxy, I'm none the less hopefully that a Toolkit-like ecosystem that is currently missing with the stagnacy of Ocelot pops up around YARP.

.NET has trimming now, so it is 5 MB? (Possibly less!)

Nope.

Running this command:

    dotnet publish `
    -p:Configuration=Release `
    -p:PublishSingleFile=true `
    -p:PublishTrimmed=true `
    -p:RuntimeIdentifier=win-x64

gives an 11 MB file, that still requires 4 DLL as well.

Pretty similar except for multi-cluster support, but I'd also call out https://octant.dev as a pretty great cluster GUI.

Also closed source and appears to plan on having a pricing model later on.

That's because the issue they're trying to solve is being slowed down by existing JavaScript tooling and infra. This is very explicitly to improve Dev UX. And they already called out the most important concern when switching to a new lib:

> The framework is heavily optimized for performance.

The intent of this RFC is to improve the places where JavaScript is already used like management tools and editing.

You may only need 10 bytes of info, but that JWT is a lot more than just a data blob. It's a signed set of user info. If you don't need that extra layer, sure, then drop to an opaque token. Complaining that a signed header is large, however, seems a little silly. It's also worth mentioning that HTTP/2 also does header compression which helps with this.

The title should be more something like "The State of AWS Lambda". The FaaS/Serverless ecosystem is larger than AWS Lambda.