[brnt]

Sharepoint is in-org, and lo and behold, that's not always, or not even usually how documents are formed.

Plus, Sharepoint still has no concept of concurrent editing, so you better hope that nobody works on the same document at the same time. Also, it doesn't track changes.

It is only better than a file on a Windows share by a hair. A very thin hair.

Word's diff is Not Great (tm), but yes, at least it's there. Have you tried using it with more than 1 other changeset?

[JonAtkinson]

These assertions are just not true. I'm working right now on a document with coworkers, concurrently, via a Sharepoint server. Change tracking is enabled and can even be enabled by default by the Sharepoint admin.

I share a lot of your sentiment about open formats in previous comments, but this is classic FUD and demonstrably wrong.

[brnt]

Then our Sharepoint server must have disabled sth. I regularly get a message on save that the document has changed meanwhile, with the option to overwrite those changes or discard my own...

No change tracking is visible to me, other than a timestamp and name of last edited.

FUD is isn't. Please don't use buzzword gratuitously, I know _a lot_ more about the deployment here than you. Also, you didn't counter the statement that it doesn't do concurrent editing (like Google Docs, OnlyOffice), which in 2024 is a major gap imho.

[JonAtkinson]

Your original comment was speaking in general terms, about all Sharepoint services. Not your specific deployment. Details matter or your argument falls down.

As for concurrency, read my comment again, I use the specific word.

[brnt]

If you see that I talk about a certain config of Sharepoint, it's much faster to point that out than being argumentative.

What did you do to have concurrent editing (or what did you not do), and how does it integrate the various diffs?