dyon VS fornjot

Reminds me of Dyon, a scripting language for Piston.

It's dynamically typed and uses lifetimes instead of a garbage collector.

https://github.com/PistonDevelopers/dyon/issues/173

This should be a good use-case for rust-based scripting languages, I think.

I loosely followed a project of that kind a while ago, I don't quite remember if it was Gluon [0] or Dyon [1]. Not sure if these are still active, or if another competitor showed up in meantime.

___

[0] https://github.com/gluon-lang/gluon

[1] https://github.com/PistonDevelopers/dyon

Dyon

These are the scripting languages i saw recently gluon, gleam, dyon, rune, mun. I like mun most because it resembles rust most. There is also this and this thread.

https://www.fornjot.app/ is an attempt, and also good at showing what a large undertaking such a goal is

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

There is so much wrong with this article. Throw a little bit of ML pixie dust on everything for more hype? Check. Compare wildly different things as if they were the same? Double check.

digdugdirk has the right idea, and AFAIR, there is some work on that front (https://www.fornjot.app/).

Also the Fiat 500 goes 100km on about 4l of gas, while the Ford F150 uses 7l. No clue where the author gets the idea that the Fiat would get worse mileage, perhaps he's dividing by weight?

The rest, I don't even.

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.

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 guess from a high-level, there are two good ways to help: 1. Pick an issue and work on it. 2. Try out Fornjot, compare its shortcomings to the list of open issues and the feature wishlist, and open issues as required.