To avoid that, bookmark this address:
https://forum.freecadweb.org/
and login there. Then you are directly in the forum.
To avoid that, bookmark this address:
I agree with all of that. I was only wondering why we need to invest manpower to change existing definitions. There was no disadvantage as they were. The code was (maybe even better) readable as now.
Really? I would never have thought of that!uwestoehr wrote: ↑Sun Sep 18, 2022 10:51 am To avoid that, bookmark this address:
https://forum.freecadweb.org/
and login there. Then you are directly in the forum.
... and have Apple in .
Maybe to you the code is like a favourite old coat. Its is ugly and broken and certainly last century's fashion but you are very comfortable in it, even if you look like a tramp when you wear it.
What is the problem then?
Ehm, no. Please re-read my post. Our code needs improvements in many areas.
Sorry, I cannot follow you. How can you judge the UI "crap" (I don't like words like this, given the countless hours many volunteers spent) without knowing what it is for? And how can you judge at all how good/bad code it by saying you don't know what it is for.berniev wrote: ↑Sun Sep 18, 2022 10:10 pm I have no idea how Part, PartDesign or TechDraw work, why they are even necessary, or what it is exactly they do. All I wanted was a simple alternative to Sketchup after they went web. But I found FC gui to be crap and when I mentioned this was effectively told don't bother us, we like it as it is, or fix it yourself.
Ahh, memories. I said most of these things 40 years ago in my first job after university. A lot of the code I said it about is probably still running and still a mess. Such is the lot of a maintenance programmer.
https://www.indeed.com/q-Mainframe-Lega ... b951aff5e0berniev wrote:Legacy code is not a career move for young programmers