µcad: New open source programming language that can generate 2D sketches and 3D

Use cases and audience

  • Many see µcad as another entry in the “programmatic CAD” niche (like OpenSCAD, CadQuery, KCL), mainly attractive to programmers and hobbyists rather than mainstream mechanical CAD users.
  • Some programmers strongly prefer code-based modeling and find GUI CAD learning curves prohibitive; others say even simple real-world parts are much faster and more intuitive in tools like Fusion 360/Onshape.

Comparison with OpenSCAD and other tools

  • µcad is viewed as “OpenSCAD with strong types and Rust-like syntax,” plus units, libraries, plugins, and a more graphics-focused design.
  • Skeptics ask what concrete advantage it offers over OpenSCAD, which already has a mature engine, instant preview, and a big ecosystem.
  • Several alternatives are mentioned (FreeCAD, build123d, KCL/Zoo, Fornjot, DeclaraCAD, ShapeScript, etc.), highlighting a crowded space.

Language design and features

  • Liked: strict typing, explicit units (e.g., mm, degrees), modular programming, better library system.
  • Disliked by some: Rust-style syntax vs C-like OpenSCAD; worries that required units/degree notation may be verbose if heavily hand-typed.
  • Lack of a constraint solver is seen as a major limitation for parametric design; people don’t want to hand-maintain “walls of trig.”

Workflow, visualization, and kernel

  • A key OpenSCAD strength is immediate 3D feedback on file save; users explicitly want an equivalent workflow in µcad.
  • A viewer/preview is reportedly in development, with hints of VS Code integration, but details are unclear.
  • µcad is based on Manifold (mesh-based), so it’s closer to OpenSCAD than to BREP-based kernels used in higher-end CAD. Export/STEP support status is unclear in the thread.

AI and code generation

  • Commenters note that code-CAD is well-suited for LLMs, though experiences with LLMs producing correct 3D models are mixed.
  • Some see µcad-like languages as a way to let non-experts generate parametric parts via natural language.

Website, docs, and branding

  • Strong criticism of the site: slow, PHP query URLs, cookie banner, some broken/removed links (e.g., Spirograph example, later re-added under a new URL).
  • Requests for clearer, static front-page examples and a PDF book export.
  • Brief debate over the logo resembling a swastika and the prominent use of “LEGO” in examples, with warnings about LEGO’s trademark enforcement.