early-stage b-rep CAD kernel, written in Rust

Weekly Release - Experimentation

A week ago, I reported how I got inspired by a talk I've seen, and my time since then was dominated by experimentation, with some promising first results!

My goal is to make the Fornjot kernel interactive. Right now, you more or less launch it with some input, then get back the results. I want to be able to inspect it while it is running, to understand exactly what is going on at every point. The immediate benefit should be that debugging the kernel becomes easier. If it works out like that, this could help accelerate development in the future.

I've been prototyping an architecture that enables this interactivity. The results are promising, in that it's possible now to inspect exactly what a core part of the kernel does over time, without that complicating any other parts of the code. However, there is no tooling that makes use of this new capability yet, so it's hard to judge how useful it is going to be in practice.

I want to wrap up this initial experimentation quickly, then continue this work on the side. While I believe that this is going to be very beneficial for Fornjot's further development, there is so much more important work to do, and I can't afford to have one thing take over my time completely.


Fornjot is supported by @webtrax-oz, @lthiery, @ahdinosaur, @Yatekii, @martindederer, @hobofan, @thawkins, @bollian, @rozgo, @reivilibre, and my other awesome sponsors. Thank you!

If you want Fornjot to be sustainable long-term, please consider supporting me too.

End-user improvements

Improvements to Fornjot and its documentation that are visible to end users.

Ecosystem improvements

Improvements to Fornjot components that are relevant to developers building on top of those. These have an indirect effect on end users, through fixed bugs and improved robustness.



Internal Improvements

Improvements that are relevant to developers working on Fornjot itself.