cq-flake VS oce

I agree with you. That's why in the past I made this issue: https://github.com/CadQuery/cadquery/issues/153

The developers don't seem to be receptive. But fortunately a nix flake exists: https://github.com/marcus7070/cq-flake

Takes ages to compile thought so I advice you to either be patient or add the cache.

Yes I agree. Anaconda is one of the worst pieces of software on earth. In fact I have never gotten it to work with anaconda. I use this nix-flake: https://github.com/marcus7070/cq-flake which is faaaaar easier to use and setup and includes the editor. But the README says it probably won't work on non-nixos systems so your mileage may vary.

Have a look at https://github.com/tpaviot/oce/ Not sure if there is a go wrapper for it. There is a python library wrapping opencascade already.

Some parts of the 3MF are actually good. I like the spec documents winding order of the meshes. The format includes units, and these optional 4x4 transformation matrices — both are useful.

As for need of the new formats, for one, modern CAD formats are insanely complex. These IGES/STEP/BREP files require many megabytes of very complicated code to deal with, such as this library https://github.com/tpaviot/oce These formats may even contain proprietary extensions. Also, they need non-trivial processing power to handle. Many people wouldn’t want a Core i7 with gigabytes of RAM in their 3D printers, inflates hardware cost and software complexity.

Besides, we now have high-resolution 3D scanners, and CAE software which algorithmically optimizes models by running numerical simulations. They both output triangle meshes instead of CAD files. Scanners often output point clouds one can convert into triangles, but hard to convert into CAD formats.

I just don’t like the 3MF implementation too much. XML is fine for kilobytes of data, but not many megabytes. If I would be designing that format, I would probably made it binary. Maybe EBML https://en.wikipedia.org/wiki/Extensible_Binary_Meta_Languag... would work for that; it does fine for MKV videos, which is also a huge pile of structured data with non-trivial performance constraints for producers and especially parsers.

Another minor thing, it was not the best idea to make name start with a digit. Most programming languages forbid identifiers like that for their classes / functions / namespaces / modules.

Cadquery uses opencascade under the hood. I think your best bet is to open an issue and ask: https://github.com/tpaviot/oce