I think you misread the issue; it's not a commit conflict. There was no second party. It's just a `svn mv` of a directory. I agree that is anecdata, yet I've h

I think you misread the issue; it's not a commit conflict. There was no second party. It's just a `svn mv` of a directory. I agree that is anecdata, yet I've had 10y of extensive experience with subversion and 10y of extensive experience with git (plus a sprinkle of cvs and rcs to boot), both used on FOSS and company contexts. I've regularly teached both to beginners ans seasoned developers alike over the years. I've had the occasion to do things with both that would make many blemish and faint. Dismissing the counterexample with "everyone's different" is a bit hard of a handwave. I stand by my assessment: subversion looks easy on the surface but is fatally flawed down to the most simple actions, to the point of being able to cause data loss.