OpenVDB VS manifold

In the README there is a section title "On the shoulders of giants" that probably points to the main reason. This project is a layer overtop https://www.openvdb.org/

Small in a relative sense compared to some larger codebase.

Here's a bit on Manifold:

https://github.com/elalish/manifold/wiki/Manifold-Library

and the author's blog is interesting:

https://elalish.blogspot.com/search/label/Manifold

For cad kernels I highly recommend manifold https://github.com/elalish/manifold

Our project https://github.com/elalish/manifold made use of this to speed up mesh processing algorithms a lot.

Wondering why no BRep support means it is not a CAD. It seems that OpenVSP doesn't use BRep but uses parametric surface [1]. I wonder if mesh-based modeling + some constraints solving will get you a CAD, or are there other requirements that I don't know? I only work on mesh processing library on my free-time and I don't know much about BRep.

[1] https://github.com/elalish/manifold/discussions/549#discussi...

Unhealthy relationship with keyboards? Comparing with the r/MechanicalKeyboards or r/ErgoMechKeyboards people this relationship is more like divorced...

I added python binding and ended up being on of the devs for https://github.com/elalish/manifold because OpenSCAD is too slow for my modeling (I am quite impatient). Optimizing my keyboard for months with more than 5 complete rebuilds to optimize my design (looks like this: https://i.redd.it/xtf0f54mt7ya1.jpg), and is afraid of open sourcing it because my code looks too bad :(

Now much faster and more stable thanks to the Manifold engine (https://github.com/elalish/manifold): in fact it is often faster than the last stable desktop release from https://openscad.org/.

Also much better code completion, and ships with a few examples from the various bundled libraries to get you started.

At the end, they gonna replace it with ( elalish manifold.