From a naïve point of view, it would seem like overkill to run a whole web browser when a few kilobytes of memory is all it really takes to draw a widget on screen.
Platform vendors like Apple, Google, MS don't want to let developers target multiple ecosystems - they want a monopoly on devs and users, hence the endless churn of languages, frameworks and SDKs, making it difficult to keep up.
It's much easier and more reliable to use HTML, even if the experience isn't as slick for users.
Is this actually true? As in, I see how we may arrive at the same outcome anyway, but at this point, do those companies actually care about aggressive lock-in?
- Apple seems to be more ignoring the possibility of SwiftUI on other platforms rather than actively preventing it since https://github.com/Cosmo/OpenSwiftUI (dead) exists. Sure, they will never help to make it happen, but "don't want"?
- Google is pretty much cross-platform/-ecosystem with Flutter which explicitly supports iOS.
- MS seems to have given up with Win Forms opensourced and working on .NET Core / Mono.
MS does not care what OS you use anymore. They want users of all operating systems to order their Office 365 license and run all their cloud compute loads in Azure.
As for MS open sourcing .NET Core it's all good and nice, but WinForms and WPF are still Windows-only, and according to MS they will remain this way. And Apple has no intentions of doing the same with SwiftUI.
"Support for Winforms 1.1 and 2.0 has been completed, and is now in a maintenance/bug fixing state."
"System.Windows.Forms implements its own driver interface to communicate with the host OS windowing system. Currently, we have drivers for X11, Win32, and macOS. These drivers translate the native window messages into WndProc compatible messages, to provide as much compatibility with native .Net as possible."
WPF is windows-only though.
I tried to use Mono several times, starting from Ximian and Xamarin times, and I always encountered strange problems that were not present in the original applications. I hope they improved somewhat recently because the code produced back then was often unusable (e.g. huge leaks after a couple of hours of use.)
the native grumpy old people like me will continue to use Windows forms or WPF or MFC,ATL,Win32.
The masochists will try to use the open-source silverlight replacement. Moonlight?
The futurists will use Avalonia. Maybe SAFE stack MVU via Fable?
The Microsoft contractors will use WinUI3.
Vast majority of web developers today will use electron, as unfortunate as that is...
Your Silverlight replacement would be OpenSilver.
The cross platform toolkits would be MAUI (nee Xamarin) and Blazor.
Electron is the new Active Desktop/XUL, its fashion phase will eventually fade away.
Can you share the official source of this statement?
Mono is not meaningfully cross platform and is not the official Windows SDK.
The iOS SDK is not cross platform and changes frequently leaving behind it a trail of dead x-platform projects like the one you cite.
I suppose there are multiple reasons for this lack and it may not be a deliberate strategy in all cases but there is no incentive to promote cross platform work and there are multiple incentives for corps not to. These platforms are made to corral users and devs, not to share them.
If you need to draw a widget on the screen, there's Dear ImGui [1] that you can use from Go [2]
If you're looking for a desktop toolkit, there's a reason why things like Qt are multidecade endeavours.