[leighleighleigh]

Hell yes, this looks awesome - do you see a future where Gazebo uses this as a physics engine?

Also just in case you were unaware, the name 'nox' refers to a popular Python testing framework... so if you were to release 'nox-py' on PyPi it would be a bit confusing. Maybe "nox-ecs"? Sorry to be a bummer!

[sphw]

Yeah I recently found out about `nox` in the Python world. That combined with someone squatting the crates.io name might make us change it completely. Our Python library right now installs as `elodin`, and we might just stick with that

[some1else]

Stick with `elodin` everywhere. Make sure to register the vendor name at all the package managers for languages you might make a library for.

[leighleighleigh]

ahh what a bummer... 'naming things' continues to be an ongoing challenge in programming lol

[sphw]

Re: Gazebo - it's possible, but IMO Gazebo likes to approach things from a slightly different angle. Gazebo uses, mostly, config files to create your simulation whereas we prefer people to use code. Someone could certainly build a physics engine using our tools, and connect Gazebo to it. We are building our own Gazebo-esque frontend, that will have a better UX long-term for our framework

[leighleighleigh]

keen to see it! I'll definitely give it a whirl using ReRun as a front-end, it looks like it would pair really nicely.

[sphw]

You can try out the frontend online at https://app.elodin.systems/sandbox/hn/cube-sat or you can install the desktop version using pip: `pip install elodin` and then run `elodin editor cube_sat.py` against this file https://github.com/elodin-sys/elodin/blob/main/libs/nox-py/e...