←back to thread

303 points vyrotek | 4 comments | | HN request time: 0.011s | 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 #
password4321 ◴[] No.45895301[source]
Except WinForms, spectacular for Windows-only utility GUIs.
replies(4): >>45896304 #>>45896925 #>>45897084 #>>45897488 #
1. glzone1 ◴[] No.45896304[source]
No kidding - kind of wild that winforms is still kind of a gold standard experience today! I actually liked VB Forms - lots of easy rapid application development was possible.
replies(2): >>45896683 #>>45902421 #
2. issafram ◴[] No.45896683[source]
WPF as well
replies(1): >>45902431 #
3. memsom ◴[] No.45902421[source]
Delphi was the best RAD tool though. It was native code, not a weird interpreted or jitted app. It could also build to a single exe file. VB struggled with an unwieldy engine for most of its life.
4. memsom ◴[] No.45902431[source]
I like WPF and I code with it regularly, but the drag and drop UI builder was the worst aspect of WPF and generated terrible Xaml that was almost impossible to maintain.