4 ms·

Because MS always do half the job and call it done (I'm a C# dev btw). Take Windows for IOT for example: if you read the presentation and the articles you woul

Because MS always do half the job and call it done (I'm a C# dev btw). Take Windows for IOT for example: if you read the presentation and the articles you would think it's a viable solution. I tried to develop a really simple app on it for work. The thing was so slow that I couldn't even make some scrollable text without lag! The same raspberry with Linux is perfectly fine. If you really want to "understand" Microsoft, just take a look at their UI frameworks: WinForms, WPF, UWP, the javascript one I forgot the name of, and now it's WinUI.

rochak 6y ago
Man, what is it with Microsoft and acronyms?
- jmnicolas 6y ago
  It's so that you need to pay an expensive consultant with the right certifications to explain you all of that ;) I'm half kidding here, especially when you know that there is a certification about MS certifications (and it's not a joke, the thing is quite complex to the point we don't do this in house).
WorldMaker 6y ago
> If you really want to "understand" Microsoft, just take a look at their UI frameworks: WinForms, WPF, UWP, the javascript one I forgot the name of, and now it's WinUI. The UI framework inside of UWP is just another name for first two versions of WinUI. That JS one you forget the name of was a version of WinUI in the early UWP era, that Microsoft stopped supporting because everyone told them the priority was Electron and React Native (and also because their browser team moved out of UWP/WinUI and over to Chromium). (Unless you are thinking of Silverlight, which was "WPF lite".) WPF itself can be considered a Version - 1 of UWP/WinUI, and today with WinUI 3 allowing you to use many of the controls directly in WPF (and WinForms), further blurring the lines between past/present/future versions of the same XAML-based rendering stacks that Microsoft has been trying to get right for many versions now. It's fun that they never settle on a strong single brand name, of course, but from a technical perspective there's a definite through line (all the way back to Longhorn's "Avalon" dreams and the original invention of XAML).

rochak 6y ago

Man, what is it with Microsoft and acronyms?

jmnicolas 6y ago
It's so that you need to pay an expensive consultant with the right certifications to explain you all of that ;) I'm half kidding here, especially when you know that there is a certification about MS certifications (and it's not a joke, the thing is quite complex to the point we don't do this in house).

WorldMaker 6y ago

> If you really want to "understand" Microsoft, just take a look at their UI frameworks: WinForms, WPF, UWP, the javascript one I forgot the name of, and now it's WinUI. The UI framework inside of UWP is just another name for first two versions of WinUI. That JS one you forget the name of was a version of WinUI in the early UWP era, that Microsoft stopped supporting because everyone told them the priority was Electron and React Native (and also because their browser team moved out of UWP/WinUI and over to Chromium). (Unless you are thinking of Silverlight, which was "WPF lite".) WPF itself can be considered a Version - 1 of UWP/WinUI, and today with WinUI 3 allowing you to use many of the controls directly in WPF (and WinForms), further blurring the lines between past/present/future versions of the same XAML-based rendering stacks that Microsoft has been trying to get right for many versions now. It's fun that they never settle on a strong single brand name, of course, but from a technical perspective there's a definite through line (all the way back to Longhorn's "Avalon" dreams and the original invention of XAML).