Yeah, the different, incompatible assembly plugins is why I stopped using FreeCAD a few years ago.
That's reportedly been fixed (guess they picked a winner?), but I haven't taken a look since. I probably will, at some point, but I generally have a different focus these days.
They didn't pick a winner. They (Ondsel and others) evaluated all the workbenches, chose the best ideas and built a new workbench around a new (well, new to C++) solver.
It is. The chap they hired to do port his solver has done really great motion solving work in the past (and, amusingly, had an application called "FreeCAD" before FreeCAD existed).
You just reminded me that I had tried Catia once before and that it also completely flummoxed me in how unobvious its approach was.
Now why would anyone choose that program as the one to base theirs off of, it isn't like Pro/E and SolidWorks weren't around in 2002 when they started FreeCAD.
FreeCAD seems to operate in the same way as Catia (ie v5/v6), or at least have been developed to follow the same approach to things.
Saying that as I used to use Catia years ago, so the FreeCAD approach wasn't completely foreign.