StationIapetus VS three

Check Station Iapetus, "commercial project that will eventually be released in Steam".

Besides being clear and easy to use, one of its popular features is the scene editor, which provides a scene preview as demonstrated in this example:

Thanks! I do have two pretty big games written with the engine - https://github.com/mrDIMAS/StationIapetus and https://github.com/mrDIMAS/rusty-shooter . I've started writing them because it is impossible to get right feature set, without a game that uses it.

Thanks! Huge breaking changes in the API are rare, I'm trying to design the API to be good from the first try. I have three dependent projects, so every breaking change forces me to fix all of those. Usually I need an hour or so to make it compile again, even on large projects like this.

Station Iapetus - https://github.com/mrDIMAS/StationIapetus

Rust has ways to deal with mutability. Three-rs [1] uses a classic scene graph tree, like ThreeJS. It's based on Froggy [2], which is a general low level primitive for building a "traditional" topology of the classes.

[1] https://github.com/three-rs/three

I had similar motivation back in the day for CGS in https://github.com/kvark/froggy, which was also powering https://github.com/three-rs/three. It's nice to see Rust ecosystem not locking itself on ECS, even if they are so cool :)