|
Easy answer to your last point: Work machine and Non-work machine. If I'm working for a company and the company needs MS Office, they will give me a machine with MS Office. I will treat that machine like a radioactive zone. Full Hazmat suit. Not a shred of personal interaction with that machine. It exists only to do work on and that's that. The company can take care of keeping it up to date, and the company's IT department can do the bending over the table on my behest as MS approaches with dildos marked "Copilot" or "Recall" or "Cortana" or "React Native Start Menu" or "OneDrive" or whatever. Meanwhile, my personal machine continues to be Linux. This is what I'm doing at my work now. I'm lucky enough to have two computers, a desktop PC that runs Linux, and a laptop with Windows 11. I do not use that laptop unless I have to deal with xlsx, pptx or docx files. Life is so much better. |
A variation I've done occasionally is to run the Microsoft Windows software in a VM on my Linux laptop.
When I last had the MS office suite inflicted upon me, a couple years ago, I was able to run it in a Web browser on Linux.
It's important to remember, though, that these measures probably won't work long-term.
Historically, MS will tend to shamelessly do whatever underhanded things they can get away with at that point in time. The only exception being when they are playing a long con, in which case they will pretend to play nice, until some threshold of lock-in (or re-lock-in) is achieved, and only then mask-off, with no sense of shame. (It's usually not originating bottom-up from the ICs, and I know some nice people from there, but upper corporate is totally like that, demonstrating it again and again, for decades.)
Also, a company requiring to run Microsoft software is probably also a bad place to work in other regards.