When I read the quote, "highest possible compatibility", I recalled the problems I had in my Microsoft-dominant office after I shared some files I edited at home using libre-office. No one was ever prevented from working on the files I saved, but my xls exports from libre-office were annoyingly affected.
I wonder if it's not just the sort of annecdote between techies and non-techies which makes the difference. I think a non-techie will ascribe too much weight to their user-experience (a file doesn't display the same when sharing files) and conclude the file is somehow corrupt or unreliable.
At best, I suspect office workers, whose work is absolutely and entirely within the realm of email, text docs and spreadsheets, don't have the patience to deal with these irreularities.
Or, at worst, in a hard-driving efficiency oriented workplace minor inconveniences add up. I tend to favor CSV to xls to begin with, but this clearly adds additional steps when I utilize functions which can only be saved natively.
For myself, I'm inured to these inconveniences from web and software development and ignore the efficency costs in some office-task-contexts (txt, csv, email) because I'm already committed to working with specific workflows.
I wonder if it's not just the sort of annecdote between techies and non-techies which makes the difference. I think a non-techie will ascribe too much weight to their user-experience (a file doesn't display the same when sharing files) and conclude the file is somehow corrupt or unreliable.
At best, I suspect office workers, whose work is absolutely and entirely within the realm of email, text docs and spreadsheets, don't have the patience to deal with these irreularities.
Or, at worst, in a hard-driving efficiency oriented workplace minor inconveniences add up. I tend to favor CSV to xls to begin with, but this clearly adds additional steps when I utilize functions which can only be saved natively.
For myself, I'm inured to these inconveniences from web and software development and ignore the efficency costs in some office-task-contexts (txt, csv, email) because I'm already committed to working with specific workflows.