libfive VS rapidyaml

Guile/Scheme: https://libfive.com/

You probably have already seen this, but I would take a look at libfive for inspiration

https://libfive.com/

You can find a few algorithms online (such as csg.js and libfive), but most of them are either not robust or fast enough for real-time graphics.

No; Bauble doesn't know how to "rasterize" SDFs into meshes; it only knows how to raymarch them. It's theoretically possible, but it's a pretty complex problem that would take me much too long to figure out and implement. So Bauble is relegated to just making pretty pictures for now. If you want to produce meshes using SDFs, check out https://libfive.com/

This is a mid-point in Matt Keeter's research.

Start at:

http://mattkeeter.com/research/thesis.pdf

then see:

http://www.mattkeeter.com/projects/kokopelli/

then Antimony (see the article at: http://hackaday.com/2015/05/29/otherworldy-cad-software-hail... ), then the current effort:

https://github.com/libfive/libfive

(and also see: https://www.gitlab.com/kavalogic-inc/tovero "a binding of Libfive to Common Lisp, including a standalone REPL-based viewer"[https://github.com/Irev-Dev/curated-code-cad] can be integrated with https://www.gitlab.com/kavalogic-inc/clive

Currently I'm using OpenSCAD (w/ BlockSCAD as a front-end: https://www.blockscad3d.com because I prefer a sort of visual representation), but have been stymied by the lack of file I/O (I want to write out G-code).

Still looking for a 3D modeling tool which is:

- a node or block editor

Interesting, I hadn't come across extism before. How hard would it be to package https://github.com/biojppm/rapidyaml in this way? (And do you have a extism for dummies guide?)

The inability, or brittleness, to embed NUL bytes into the string, for once. Zeroed bytes can be valid as an internal bytes of a longer encoded character. And the inefficiency of tempting every caller to rederive the string length on every use, leading to such bugs as quadratic parsing behavior with sscanf. The extra register for an explicit length is a very minute price to pay compared to that.

Although you still have the other problem of sscanf, where read times can become quadratic.

You are really simplifying that issue. A lot of it has to be how the implementation of sscanf works and it's super easy to abuse by complete accident when a lot of data needs to be read and parsed to correct values. See more here: https://github.com/biojppm/rapidyaml/issues/40

Leading to eye-rolling problems like these: https://github.com/biojppm/rapidyaml/issues/40