iot VS Uno Platform

On the other hand, for maximum code reuse, you can use regular .NET 7, plus .NET IoT Libraries if you need sensors/access to GPIO and so on, plus Avalonia as a GUI, which is also using XAML, but incompatible with UWP.

Try the same program but with a hardware PWM library, e.g. https://pypi.org/project/rpi-hardware-pwm/

.NET nanoFramework has support for GPIO, I2C, SPI, PWM, ADC, DAC, Serial, 1-Wire. Also the API are aligned with .NET IoT making it easy for code reuse between development on a Raspberry Pi with .NET 6.0 and an MCU running .NET nanoFramework.

You can write machine learning application using C# with the help of https://dotnet.microsoft.com/en-us/apps/machinelearning-ai/ml-dotnet. Additionally IoT development as well using C# (https://github.com/dotnet/iot/tree/main/samples/force-sensitive-resistor)

Every sensor and module out there woks with on of the standard protocols like I2C or SPI and C# supports them. But everyone wants pre-made libraries/device binding and dealing with raw I2C and SPI is frustrating. .NET also has device binding libraries and most popular devices have binding there. Meadow team is also porting their binding to Linux.

And Uno Platform (https://platform.uno/) is akin to React Native in terms of native controls usage.

also UNO Platform (C#) which is suitable for simple or complex cross platform business applications : https://platform.uno/

Why is this a problem? At face value, it isn't a problem. Taking a step back at a more global level, what does "uComponents" mean to the rest of the world? Many of the .NET developers who heavily use NuGet may have not even heard of Umbraco CMS, let alone a 3rd party plugin for it. What if people from the Uno Platform community are browsing NuGet for some kind of components extension library? You can see, this could get confusing outside the scope of the Umbraco community/ecosystem. On top of this, uComponents was developed against Umbraco v4, with its last release in 2016, now it's there to be lingering on the NuGet repository until the end of time, set in stone.

Not a fan of XAML after trying to get into it, but there is Uno Platform. It wraps native widgets on mobile, just like React Native (which is good for accessibility), and uses C#. https://platform.uno/

My guess is that it's mainly focused on mobile. On Windows, it has no overhead (behaving like a normal WinUI 3 app), on macOS I think it uses Catalyst by default (which was developed by Apple to make more iOS apps available for Mac desktops) and on Linux it draws its own widgets that the devs try imitating the GTK style with.

On Android and iOS, it just uses the native widgets which I think is a better experience so you can see my reasons for guessing it's mobile-first. That may or may not be what you want.

5- Uno

> ...building UIs with the document/element api

When the whole premise is flawed, JSX or not, does it really matter if there is a better or worse way of misusing a technology not meant for UIs?

Leave HTML and JavaScript to Wikipedia and other hypertext document libraries.

Unfortunately, WASM is not there yet, but people are trying: https://platform.uno.

Uno Platform is fully open source, under Apache 2.0 license. You can see the license here https://github.com/unoplatform/uno/blob/master/License.md

Also, .NET 7 brought a lot of stability so I am confident you'll have a better experience. I hope to hear back from you. It would be great to have any feedback at our repo - https://github.com/unoplatform/uno/discussions