As far as storing cad files as you describe, how does that interface with OpenCASCADE file formats? The data storage is related to the CAD kernel I think, so it might be difficult to move to a “store models as code” storage model.
The question of format used to store part info is more relevant to PartCAD. However I do not think PartCAD should prescribe any. PartCAD must be modular and support as many formats as it can. And let the competition decide. Maybe the supported/compatible CAD kernels will contribute to the competition of file formats. Maybe the file format chosen by the community (e.g. for LLM related reasons) will contribute to what CAD tools support. We’ll see in 20 years.
I personally don’t think the community at a whole will gravitate towards anything like OpenCASCADE file formats. I find CadQuery and build123d more promising (no matter what’s under their hood at the moment). I believe it must be human-readable (and, thus, LLM-readable) text. But CadQuery and build123d are not the end of the evolution. I’m sure we will face next technology iterations that are at least more LLM friendly, secure (e.g. to prevent arbitrary I/O from code), and more structured (to help retain the code structure and formatting in the “Load”-“Change”-“Save” cycle).
PartCAD will be there to facilitate modular design and collaboration, and to include as many people and their tools as possible. Not to facilitate any closed formats or tool ecosystems that commercial tool vendors are trying to prescribe to us today, no matter how convincing their arguments sound. Large profits enable generation of very convincing arguments.
No matter how difficult it is going to be to “store models as code”, I personally believe the humanity will succeed at that. However PartCAD will support all common file formats. It currently (2 days after a preview release which somehow went huge) supports CadQuery, build123d and STEP files.
But on the topic of CAD/CAM systems, there IS value in having a single workflow tool from design to manufacture. Fusion 360 shows how beneficial it can be to have these different aspects of the workflow be seamlessly integrated.
There’s no justifiable reason to Balkanize all the CAD tools based on function. Users don’t want that.
No one really knows what all of the users want. The commercial tool vendors would tell us that all users want exactly what they sell. My subjective experience suggested a hypothesis that some users might want something different. After two days of PartCAD’s initial revision being out there, it would be fair to say that a lot of users want it. The demand and feedback exceeded all expectations.