This is part two of our series on the need for an integrated default assembly workbench for FreeCAD. Part One gives and introduction and explains our methods. In this part, we take a closer look at Assembly 2, one of the early approaches to adding this feature set to FreeCAD.
This is the first post in the series where we discuss the need for an integrated assembly workbench, review existing 3rd-party options, and discuss takeaways from our research.
Should hiring managers base a decision on someone’s GitHub profile? No. But will it ever hurt to have a robust GitHub account? Also no.
I’m a hiring manager for a new open core company, and I watched the discussion under @manuel_frigerio’s tweet blow up with amusement. The debate about using people’s GitHub profiles to make hiring decisions isn’t new. The typical backlash ensued and Manuel has since made his tweets private. And sure, using someone’s GitHub profile, particularly their contribution graph, to judge their skills as a developer is flawed.
FreeCAD's 'topological naming problem' is legendary. It's frequently cited as the number one reason holding back widespread adoption of FreeCAD for commercial use.
Developer RealThunder introduced a fix to the problem years ago, but it has never been fully incorporated into the core product.
Will FreeCAD ever have a solution? Yes. But it’s going to take time.
Let’s back up a bit.
When Autodesk changed their license for Fusion 360 in September of 2020 there was a collective scream from the user community. Hobbyists, YouTubers, and makers felt betrayed. Now, after more than two years, we can see the effect. Many of those people left Fusion and never looked back.
On August 17, 2022 the FreeCAD community celebrated its 20th anniversary as an open source project. That was an important milestone … and it passed with hardly anyone noticing. There was another important development last year and it barely got any more attention, even though it was far more consequential.