> But that's letting them set the goalposts.
replyThis is missed in so, so very many discussions out there.
You can reproduce about 50-75% of what MS offers with FOSS and work on writing the rest in-house/in-EU.
Would a bunch of workflows suffer initially? Sure, but not even trying is just preseving the status quo.
Today I opened a .docx file on libreoffice on my linux machine. Did a whole bunch of editing and sent back the file for some semi official purpose. And the .docx file behaved as usual on the windows machine of the sender.
I mean to say for many many people the workflows will not suffer even one but. It's just too much automated people whose work may suffer initially b cause they are using windows API or something like that. But that's like just for developers suffering. Most govt offices or universities just work on individual files and that will never suffer even one bit
replyI mean, to be honest, I've historically had most software out there break in all sorts of ways, LibreOffice had some interesting issues while working on my thesis: https://blog.kronis.dev/blog/libreoffice-bibliography-is-bro... (bit of a rant back then, when I had a section on my blog called "Everything is broken", but you get the idea)
replyBut yeah, it probably depends on what you're trying to do with any one software package, some people will be affected more than others and sometimes most stuff will just work!