←back to thread

303 points vyrotek | 1 comments | | HN request time: 0s | source
Show context
mattfrommars ◴[] No.45894761[source]
In the .NET ecosystem, I have noticed people to shame .NET MAUI because Microsoft themselves don't use this framework - Microsoft Team is built on Electron and not MAUI.

Why build a product on MAUI when Microsoft aren't too sure about it.

replies(10): >>45894798 #>>45894820 #>>45894890 #>>45895144 #>>45895166 #>>45895441 #>>45895856 #>>45896444 #>>45896882 #>>45897144 #
latentsea ◴[] No.45895144[source]
Never build a frontend on a .NET technology. Period. They always end up unsupported in the end. Just use standard web technologies and thank yourself later. I've been a .NET dev for a decade now and that's what I've learnt.
replies(7): >>45895301 #>>45895556 #>>45896012 #>>45896688 #>>45897709 #>>45897973 #>>45901208 #
apatheticonion ◴[] No.45896012[source]
Tauri is pretty awesome. Rust backend, WebView front end. Nothing uses native desktop elements of course.

To be fair, there is no practical way to write native desktop applications using stylistically consistent UI elements AND have it be portable AND in a language that you enjoy using.

As far as I can tell, Windows 11 doesn't even have a toolkit with platform UI elements.

GTK on Gnome is pretty okay and GTK-rs is not dissimilar to React. Who know what MacOS uses but something something Swift XCode.

But I agree, just use web technologies. Write once, ship everywhere (and hum loudly when people complain about poor performance - joking, it's the vendors' fault we have to use web technologies).

replies(3): >>45896365 #>>45896605 #>>45897628 #
jzebedee ◴[] No.45896605[source]
> As far as I can tell, Windows 11 doesn't even have a toolkit with platform UI elements.

They do, it's called WinUI 3. It's barely used for all of the aforementioned.

replies(1): >>45897832 #
1. apatheticonion ◴[] No.45897832{3}[source]
I tried this. Their examples don't even compile lol