What did changed since Microsoft used ACPI as tool against Linux?
Enforced Auto-Updates, Ads, Cloud Account enforcement, Blocking Firefox partially in Teams [1], Setting Teams as Browser (Edge?), WSL (intent is not compatibility, it is to prevent migrations to Linux), Azure is a giant security problem and finally the deal with Qualcomm (hinder Linux on ARM) like we are in the 90ies?
The crap named Secure Boot with Microsoft as Certificate Authority. After certificates proofed to be miserable on the internet for 25 years. What about signing with a user generated private key (stored in a keyring or similar) of the superuser and storing the public key in the UEFI? Which would be simple and reliable. No. Microsoft opted for the solution which depends on their goodwill and the biggest possible attack surface.
And Pluton looks so awkward that Lenovo and Dell turned it immediately off.
I will not trust them. Their business model is greed, making the users itself hostile actor against all others. Using something intentionally incompatible and borked isn’t “your department”. You harm others with incompatible APIs, ABIs, weird “Word” files and Teams.
I didn’t considered to use DotNet. GNOME removed it a long time ago and it is fine (Tomboy/Mono -> Gnome/C++). The only thing which seems good is LSP. But the hard work is done by CLANG and others. Not Microsoft.
[1] Teams worked six months ago flawlessly with Firefox. Even screen-sharing on Wayland. But they greyed out and blocked the video-call button. Until I figured out that I can initiate calls through the calendar…lol. It is like 2001.