I think the reason is the incorrect use of Python 44.4% in FreeCAD is a lot and absurd I think FreeCAD need more C++ code if they continue to use Python for everything, the program will become unusable.
@@OffsetCAD Yes, the situation is that bad. no one can deny that it's a great program and the programmers are working hard to improve it but python will not solve the problem, fusion 360 is more than 90% c++ and the other 10% are other languages just for the cloud and stuff like that
FreeCAD devs must improve this workbench, I took days trying to understand why the problem. I updated to the last Release Candidate to find the same tedious problem. I just give up trying to figure out. Now I'm waiting to test the model in the "stable" FreeCAD 1.0.
So this is a big setback. Python is a language that seems simple to me, that problems like these could arise in FreeCAD because of Python I did not expect.
I think it is fine to have more things in Python. Python adds immense flexibility to FreeCAD which isn't otherwise possible. A better solution, in terms of functionality & feasibility, would be to move heavy operations to C++ and only have APIs in python
Amazing!
Thank you !
You're welcome!
I do like the assembly workbench.
I wonder how this performs in the dev builds as they have improved alot of general features over the RC2 buld.
I updated to v1.1dev I found new problems which I'm trying to fix.
I think the reason is the incorrect use of Python 44.4% in FreeCAD is a lot and absurd I think FreeCAD need more C++ code if they continue to use Python for everything, the program will become unusable.
Serious?
@@OffsetCAD Yes, the situation is that bad. no one can deny that it's a great program and the programmers are working hard to improve it but python will not solve the problem, fusion 360 is more than 90% c++ and the other 10% are other languages just for the cloud and stuff like that
FreeCAD devs must improve this workbench, I took days trying to understand why the problem. I updated to the last Release Candidate to find the same tedious problem. I just give up trying to figure out. Now I'm waiting to test the model in the "stable" FreeCAD 1.0.
So this is a big setback. Python is a language that seems simple to me, that problems like these could arise in FreeCAD because of Python I did not expect.
I think it is fine to have more things in Python. Python adds immense flexibility to FreeCAD which isn't otherwise possible.
A better solution, in terms of functionality & feasibility, would be to move heavy operations to C++ and only have APIs in python