manifold VS fornjot

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.

I agree 100%.

Truck[1] and Fornjot[2] are recent attempts in the Rust space, both are WIP.

But both seem to be going the traditional way. I.e. B-Rep that can be converted to (trimmed) NURBS.

I think if one wanted to incorporate the last 50 years of computer science, particularly computer graphics, one needed to broaden the feature set considerably.

You need support for precision subdivision surface modeling with variable radius creases (either via reverse subdivision where you make sure the limit surface pass through given constraints or using an interpolating subivision scheme that but has the same perks as e.g. Catmull-Clark).

Then you need to have SDF modeling ofc.

Possibly point based representations. If only as inputs.

And traditional B-Rep.

Finally, the kernel should be able to go back and forth lossless between these representations wherever possible.

And everything must be node-based, like e.g. Houdini. Completely non-destructive.

[1] https://github.com/ricosjp/truck

[2] https://github.com/hannobraun/fornjot

Fornjot seems like this question was tailored for it: https://www.fornjot.app/

I think some interesting developments are made in that sector in the form of https://github.com/hannobraun/Fornjot and https://github.com/ricosjp/truck. Let's see whether one of those will actually get anywhere near a usable level. Fornjot in particular is shaping up really well.

E.g. Rhai[2] or Lua or whatever.

And I guess if their tech is solid enough, someone will do that eventually and open a PR or fork the project. They do not use an existing geomtry kernel but do everything from scratch which makes this a very interesting endeavour.

There also seems to be a goal overlap between Fornjot and DieselCAD

[1] https://github.com/hannobraun/Fornjot

[2] https://rhai.rs/

I have heard of yet another in-development CAD software like OpenSCAD or CADQuery, called Fornjot. Still, these are not ideal.

I'm not opposed to someone else adopting that code and creating that crate though! (Fair warning though, Fornjot might not end up using that crate. We might still go with another approach eventually.)

also it's to early to be off much use to you, but have you heard of https://www.fornjot.app/ ? it's a very in development cad kernel that is also aiming for integration into multiple host languages.

Yes! The website and repository README have a screenshot, and there are screenshots for each model in the models/ directory.

I'm kind of interested in this issue because it's what I immediately wanted when I ran fj-app.