

What’s the second problem after topo naming that’s getting fixed?
What’s the second problem after topo naming that’s getting fixed?
FreeCAD has already merged the solution for the infamous ‘topological naming problem’. The 1.0 release may happen soon!
You are right, except for one detail. Package managers almost always validate the packages using digital signatures, to avoid man-in-the-middle attacks. You don’t need to trust the network anymore. Shell scripts piped to a shell don’t have that protection. You still have to trust the developers and maintainers, though.
The Apache to AGPL re-licensing seems OK - considering that many other projects in similar situation chose non-FOSS licenses like BSL. But CLA replacing DCO? What will prevent the project from going closed-source in the future, without the approval of the contributors? This doesn’t look good for the project.
OpenSCAD is a good take on CAD. My primary workflow is also based on plaintext (text configs, code, org-mode, latex, etc) and keyboard (no mouse). It’s easy to manage and back it up with version control tools like git. However, there are a few fields that I feel are inherently visual and need a very interactive tool. CAD is one of them. Others are 3D animation and art.
Mechanical CAD. Something like SolidWorks or Fusion 360.
FreeCAD just isn’t there yet. They’re still struggling with the topological naming problem. However, Blender was like this in the field of 3D animations. Now it’s the standard. That gives me hope for FreeCAD. Anyway, MCAD is very important. I’m learning modern C++ and the FreeCAD code base in order to contribute.
I also wish there was a better CAD kernel than OpenCASCADE.
It says ‘one of the most shameful’. There are plenty of others - especially the ones perpetrated by the devil Henry Kissinger. This shameful episode is right on character for the USA.