News for hackers. Stuff that matters.
Re:Show HN: SolidCraft – Open-Source Parametric CAD in Rust ... by phil-martin on Tuesday October 13, 2026 @06:02AM (#50069277)
Fascinating repo, thank you for making it!

I’m curious, what does this part mean?

“ Dangerous operations which may generate degenerate/sliver/zero-dimension geometries are instead blocked from materializing to 3D at a compiler level.”

How is that achieved, or rather what does that mean? What defines a sliver?

Re:Show HN: SolidCraft – Open-Source Parametric CAD in Rust ... by YuechenLi on Tuesday October 13, 2026 @06:16AM (#50069392)
A sliver is basically a tiny degenerate geometry in the micro/nanometer scale that's basically the result of ambiguous surface intersections. Basically, if you put two say, cylindrical surfaces against each other in NURBS form, floating point noise would generate these microscopic geometric noises, and a lot of what commercial kernel does is they use what they call "healing" operations to clean up those bad microscopic geometries from the models they generate.

Aetheris took a very obvious approach that not many have seemed to tried before: It throws an error when an operation that may create ambiguous intersections and refuses to materialize bad geometry in the first place, which is not really possible to do with traditional NURBS based kernels, whereas Aetheris can because it is analytical first.

Re:Show HN: SolidCraft – Open-Source Parametric CAD in Rust ... by SOLAR_FIELDS on Tuesday October 13, 2026 @08:16AM (#50070474)
You see slivers in 2D spatial operations as well. Imagine that you have two parcels represented as polygons that don’t perfectly spatially intersect. If you perform a boolean operation to, say, compute the union of these two polygons into a single one, any microscopic difference between the two boundaries below a certain tolerance (like 0.001 square meters) will manifest itself as tiny gaps and slivers. Most GIS engines will merge the two polygons appropriately beyond that tolerance (this is a way simpler problem in 2D space!) but if the data is bad enough you’ll definitely see it.
Re:Show HN: SolidCraft – Open-Source Parametric CAD in Rust ... by zamalek on Tuesday October 13, 2026 @11:38AM (#50073422)
While this is technically correct behavior, users will interpret that as your software not being able to do something - or as a bug (because it works on one drawing but not another).
Re:Show HN: SolidCraft – Open-Source Parametric CAD in Rust ... by YuechenLi on Tuesday October 13, 2026 @12:39PM (#50074575)
Well, this is more similar to a linter/borrow checker than anything else, because if you catch errors at compile time, the bad geometry doesn't persist in the STEP artifact that's being generated, so analogous to the philosophy of Rust vs C++ really.

The current design is meant to be import tolerant but export strict, it imported most STEP file I throw at it fine after a bunch of fixes, but I don't really have a big enough sample corpus know for sure how much real world STEP file it can handle.

Re:Show HN: SolidCraft – Open-Source Parametric CAD in Rust ... by phil-martin on Tuesday October 13, 2026 @05:21PM (#50078948)
Thanks for the explanation, appreciate it!

Sorry for asking for definitions - since Aethris is such a different architecture, I want to make sure we’re using the same language.

When you say “models they generate” do you mean the the nurbs representation, or the tessellated geometry for rendering?

On a related topic how does Aetheris perform when defining a screw thread? Or a nut thread?

Re:Show HN: SolidCraft – Open-Source Parametric CAD in Rust ... by YuechenLi on Tuesday October 13, 2026 @06:45PM (#50079991)
Aetheris generates STEP AP242 BREP directly, the tessellated mesh generated is only used for display (although currently, I've switched to a WebGPU based SDF representation so the surfaces can be smooth). One of the key differences in the architecture Aetheris doesn't export rational b-splines outside of debug or STEP passthrough and instead tries to recover and export analytical and non-rational splines instead.

On screw thread, if you mean by "how do you make a screw thread in Aetheris", you can check out the actual code for a threaded bolt I built for a showcase here with the JSON like DSL called Firmament:

https://github.com/yuechen-li-dev/Aetheris/blob/master/fixtu...

So, the high-level surface language of defining a screw thread is basically a struct/record that looks like:

    Thread MainThread {
        Surface: face(Bolt.Shank)
        MajorDiameter: 8mm
        Pitch: 1.25mm
        Length: 47.5mm
        StartOffset: 1.5mm
        }
Which is why I said that it's really hard to think of an editor UI for Aetheris that's not just a text editor or a ComfyUI like graph visual programming or something.

If you mean compile speed wise, not great right now, it wasn't that much of an issue when running on RyuJIT natively since it's still acceptable, but currently WASM cold compile speed for a moderately sized assembly is around 4-5 minutes so there is a lot more work to be done before I'm ready to put it on a cloud server.

Re:Show HN: SolidCraft – Open-Source Parametric CAD in Rust ... by imtringued on Wednesday October 14, 2026 @03:54AM (#50083958)
I'm not trying to tear this down but if your geometry kernel can't be compiled into a .dll or .so file and then included inside the CAD program I'm not sure people will be interested in running your software.

I'm not critiquing the language choice, it's just that I basically have a thing that is big on dynamic linking and I would rather farm out the geometry kernel to someone else and at this rate I'm kind of forced to port yours over so it works for me and I think that would be a bad outcome for both of us.

Also your .firmament files are good because I'm working on something like that too.