Yep. They've had version control for at least a decade, diff'ing also, by way of Compare. I'm also not sure why people are fascinated with using git here. It's weird seeing all of the complex solutions in this thread for a problem which does not exist.

Edit: I meant 'fascinated with using git here in this context'.

I suspect most people in this crowd either don't have direct experience with Office 365, or haven't discovered its versioning/real-time collab features.

That said, "track changes" is still used extensively especially with parties outside the organization, especially for legal documents.

My experience of those features a few months ago has been poor, particularly for Powerpoint, so I turned to HN for advice: https://news.ycombinator.com/item?id=23245552

Some of the proposed solutions were very nice, particularly Draftable - but it's expensive and my bosses didn't feel it was worth it. To this day they still work on huge slide decks that are partially shared, but I'm just not involved anymore with that side of things so I stopped pushing. I still think a way of tracking Powerpoint decks on a slide-by-slide basis, with partial merging and synching, would be really good to have (existing features for embedding are '90s-era).

For Word there are quite a few solutions nowadays, most are clearly superior to the stuff Office ships with. So the problem is still there, just not as bad as 15 years ago.

It already existed at the time this article was written, as well, I think. There is probably a niche for purely ergonomic tooling that works with, not against, the built-in features, but a lot of this is a matter of positioning - I know some expensive and widely used legal document management systems that are strictly worse than the built-in features (regularly lose important data thanks to user error in ways that are impossible with the built in features). They still sell and get used.