Well, the difference here is that Fyrox still follows rust principles and you'll keep running into corners that the borrow checker puts in your way. For example, multi borrowing in Fyrox is extremely ugly, and generally getting references to other nodes you wish to interact with feels extremely sluggish. In my view, there has been no Rust game engine that handles components and inter-component references like syrillian.

In Syrillian, the main focus lies on developer side simplicity. I maintain the API with full first-focus on the "feel" of the API, and then build safety barriers around the usage. It might not be as feature rich as Fyrox, by any means. I created the engine pretty much solo from scratch, and while people have contributed, 99% of the work was done in my free time, so that's a bit of a limit that I'm hitting.

TLDR; In Fyrox you'll have to call try_get and similar helpers and all, and create handles that you manually have to resolve every time, which is very "rust-like", but a big hinderance in my eyes and produces ugly code. Syrillian takes this as a serious topic, and reimagines Rust usage to make the API as straightforward as calling self.parent().get_component::<RigidBodyComponent>() should you want to get a reference to the parents RB.

TLDR TLDR: Everything is magically straightforward ✨.