Layl

I'm running into a similar issue where I just want to serve my JS and WASM from a `static/` route, but since the WASM path is hardcoded in the JS...

I personally think cgmath strikes a good balance, where nalgebra goes to a far extreme that makes it harder to use in projects. I always feel like the best approach...

64-bit floating point values are overkill for the average game. Might it be an option to add a feature "double_precision" that can be set in cargo and defines Scalar as...

Unfortunately as far as I know this would require the code to be extended to support more complex glyph formatting, and can't just be turned on with the flip of...

Looking further through how Bullet implements this, it seems to use concave collision detection for this use case, even for heightmaps (though those get some optimization). However the actual implementation...

I did some further digging, and it seems the ReactPhysics3D library takes the same approach as Bullet (including how it implements concave meshes), but its codebase is much more understandable...

To be entirely frank what this logo looks like to me is a mess of badly connected parts that don't fit well together.

I'm personally very much a fan of clean design, what if the chainring is instead replacing the O, and the other letters stay intact. It's very simple and clean.

I think the one with just the O replaced with the logo with the piston in it is nicer, it looks cleaner.

The simplest fix would be to just add another constructor that takes an XDocument directly, and have the file path constructor call into that. Anything that needs to pass it...