• pageflight@piefed.social
    link
    fedilink
    English
    arrow-up
    10
    ·
    9 hours ago

    Why is this better than the scripting environment in other CAD systems? I’m particular, I looked a bit at https://openscad.org/ previously, though didn’t make much headway modeling the thing I wanted.

    Why is a language-level approach better than just an API in an existing, popular language?

    • django@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      8 hours ago

      They mention openscad in the book:

      We loved it too and created many “thingies” with it. However, as experienced software engineers, we also had a few points of critique. While OpenSCAD is easy to learn and has a syntax reminiscent of C, we felt the language could be improved in several ways:

      • more specialization for creating graphics,
      • better support for modular programming,
      • strict typing and unit handling,
      • a syntax closer to Rust than to C,
      • a solid library system,
      • plugin support for other programming languages,
      • and a more powerful visualization concept.
      • CorneliusTalmadge@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        arrow-down
        2
        ·
        8 hours ago

        “As experienced software engineers” highlights the problem with many CAD solutions. People who design physical “thingies” professionally are generally not software engineers.

        We of course need a viable solution as an open source product but a lot of this is recreating the wheel without any knowledge of how the wheel is being used or why it is even useful to begin with. So you essentially end up with a knock off version of the wheel that doesn’t work the way someone who is experienced with wheels expects it to work.