←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 #
oaiey ◴[] No.45896882[source]
The answer to that is well known: Windows division builds WinUI/Win32 as their native C++/COM API, Office division went to React on their path to the web and the dev division fills gaps (WPF) and provides tools for external and internal devs (Maui for cross platform uis).

It is history not the lack of will. At one point the windows division was in shambles (remember vista) and WPF pops up. At another point, the windows and dev division have no answers to the office group (because you know who uses non win tech) so they went react. And then external devs screamed: where is the .net cross platform story so Microsoft acquired xamarin and later form Maui out of it.

It is history not lack of trust. But the outcome is the same: lackluster support for all UI toolkits.

replies(5): >>45897071 #>>45897145 #>>45898310 #>>45899431 #>>45901180 #
TiredOfLife ◴[] No.45899431[source]
> Windows division builds WinUI/Win32 as their native C++/COM API

Windows for many years is just a pile of different browser engines stashed one atop another running broken javascript/xml with react native on top.

replies(1): >>45901173 #
1. vjvjvjvjghv ◴[] No.45901173[source]
At the bottom of everything is Sharepoint though.