top | item 47154387

(no title)

Robotbeat | 5 days ago

This isn’t accurate. FreeCAD merged the main changes from that fork (RealThunder) to fix (well, mitigate) the problem. That’s the big thing with 1.0.

Although… as others have noted, this is a problem with basically all CAD packages, as on a fundamental level, it depends on user design intent. Just some have enough bandaids that it’s more rare.

discuss

order

groos|5 days ago

My statement was accurate as of _when_ I moved away from FreeCad. I'm happy they merged the RealThunder work. But they dilly-dallied for a long time while people were demanding a fix and one was available. Doesn't speak well of their org politics.

obelisk79|4 days ago

The org politics (which has actually improved tremendously in the last 3 years), in particular related to realthunder's solution, was related to code compartmentalization and maintainability. Yes realthunder's solution worked, and he submitted massive monolithic PR's to FreeCAD main for integration and then basically disappeared. Ultimately, it ended up getting chunked out into smaller parts and reverse engineered and restructured by a couple of other FreeCAD dev's under grants paid for by FreeCAD and it took them about a year to accomplish. The man who did the bulk of the work, Brad McLean, unfortunately died shortly before 1.0 released with all of his work included in it.

Not trivial work.