EdenSCM VS svd2rust

Kind of weird that https://github.com/facebookexperimental/eden (linked in mononoke) redirects to sapling. Does that mean it's replacing eden?

Maybe at their scale it makes more sense to switch to a VCS like Eden? https://github.com/facebookexperimental/eden

Eden's equivalent of 'git status' should run almost instantaneous, as checkouts are hosted by a virtual file system (FUSE) that tracks changes.

Meta having moved on from Mercurial may be a factually true comment, but it looks like they still have fondness for Mercurial's ways:

https://github.com/facebookexperimental/eden

> - A build system / package manager like Nix [1] but with a better user experience / more straightforward command-line tooling.

Working on it :)

> - A version control system which scales to petabytes or more. Something that I could put large video files in without thinking twice about it. Something a large company could use for their monorepo—or even their data warehouse.

https://github.com/facebookexperimental/eden

> A note-taking tool that allows me to organize notes in a graph with links between them

https://www.orgroam.com/

Eden - a cross-platform, scalable source control management system from Meta.

Eden\ (202 comments)

https://github.com/rust-embedded/svd2rust

Additionally, I use vanilla VS Code and rust analyser so no need to use manufacturer supplied lock-in IDEs. There are many compiler targets to choose from for cross compilation and tools like probe-run to flash chips.

One major issue is lack of manufacturer provided code examples written in Rust. For that I rely on the Rust community. A typical example being nrf-hal for Nordic Bluetooth chips.

In the case of rust you can use svd2rust to automatically generate types that represent registers on the hardware you are working with if you have a svd file. This can generate a lot of code depending on the hardware you have.