Zoo and openSCAD both create 3D objects using code in a domain specific language. Other than that, very different. OpenSCAD has limited ambitions; Zoo wants to

Zoo and openSCAD both create 3D objects using code in a domain specific language. Other than that, very different. OpenSCAD has limited ambitions; Zoo wants to kill Autodesk. Zoo is building a commercial grade product suite from first principles. They're writing a new geometry kernel and optimizing it for GPUs. They wrote a new domain specific language for CAD [0]. They're running the kernel on the cloud behind an API, streaming video to the client and billing by the server-minute. Ideally that will deliver great performance and keep the tool accessible to casual users. The really exciting thing, for me anyway, is they want to unify design-by-code, design-by-mouse, and design-by-ai. Start with a plain language description of what you want. Get a fully parametric object on your screen. Click around making adjustments. Pull up the code and make precise changes. Keep a complete changelog in git. Anyway, much more detail here: https://zoo.dev/blog/mechanical-cad-yesterday-today-and-tomorrow https://zoo.dev/blog/mechanical-cad-yesterday-today-and-tomo... [0] https://github.com/KittyCAD/kcl-samples https://github.com/KittyCAD/kcl-samples