JoltPhysics VS wg

There is now also https://github.com/jrouwe/JoltPhysics which is used in Horizon Forbidden West.

Apparenty, this is a game engine used by Horizon Forbidden West and I was curious what you all think about this project: https://github.com/jrouwe/JoltPhysics

As far as physics engines go: Jolt currently seems to kinda disrupt the decade-long equilibrium, at least as far as I'm aware:

https://github.com/jrouwe/JoltPhysics

No, they replaced Bullet with Jolt. That is considerably more than "some adjustment", regardless of what you think of the result.

A multithreaded rigid-body engine for games: https://github.com/jrouwe/JoltPhysics

Would you rather they use Jolt Physics? https://github.com/jrouwe/JoltPhysics S&box is thinking of using this engine instead of Source 2's Rubicon. As they say, maybe someone could / would hook up Jolt as a GDExtension.

Inspired by James Munns's call, and as 2023 is coming to an end, I figure it's a good opportunity to reflect and look forward to 2024. It's been a bit over 1.5 years since I embarked on my embedded Rust journey and it's been nothing less than exciting since. So here it goes.

Because you are an embedded guy. There is the https://github.com/rust-embedded/wg working-group. Rust on embedded is really on a got track forward. There are many chips/vendors that are supported both in no std / std rust world, but still there is a lot of niche things where you can actively help to be the first to get it run in Rust.

To specifically answer your question, here:

* <http://www.areweembeddedyet.com/>

It currently redirects to:

* <https://rust-embedded.org>

Which doesn't really contain anything other than a link to <https://github.com/rust-embedded>.

(via <https://github.com/rust-embedded/wg/issues/15>)

Then the Rust Embedded workgroup provides: - Direction on how to using generics and zero-sized types to achieve functional safety - svd2rust, which provides safe abstractions to peripheral access from SVD files and achieves this functional safety - The embedded HAL spec, which makes porting to different vendors/hardware easy - Peripheral access controllers and HALs for various vendors & hardware

The Rust Embedded Devices Working Group curates a list of useful embedded Rust resources, including Peripheral Access Crates (autogenerated from SVD files), embedded-hal Implementation Crates (hand-written libraries implementing the traits (interfaces) specified by the embedded-hal), and Board Support Crates.

You should also look at https://github.com/rust-embedded/wg/issues/41 and https://github.com/rust-lang/rust/pull/55011#issuecomment-429336055.

Here's an interesting discussion, consolidated here. My view is you should use a restricted scope atomic (as best as can be supported) and interact with that through a handler struct. I.e. no global state.

Most of the issues are explained in EWG RFC 419. The TL;DR is that some resources need to implement Send to be usable from interrupts, but they must not be sent across cores.