crates.io VS mun

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.

So this is my question: Which way was the right to find it out? There is no info about this feature on crates.io. I also have no clue what exactly it does and why it is named rwh_05.

Rust does it so much better with https://crates.io . I don't know why Go can't (or won't) do something similar.

Mun is a statically typed language that compiles to machine code with LLVM, designed to be hot-reloadable: https://mun-lang.org/.

Perhaps https://mun-lang.org? Might be a bit raw for your needs tho.

But that’s not all! In total, this release contains 111 pull requests made by 5 of our community contributors and our two Core Team members & Dependabot. Thanks for having our back! For a full list have a look at the changelog, but the main improvements are:

Whenever I read about Mun, I'm always really, really intrigued… Until I remember that it currently has no string type and support for one is not currently planned. That's a bit of a shame, IMHO, because otherwise, this looks great!

There's mun [1] which is statically typed and AOT compiled.

1: https://github.com/mun-lang/mun

From the reverse-dependencies of the salsa crate, the (archived) Lark compiler used it and the Mun compiler uses it.

I notice that there are projects like mun trying to achieve a similar goal, but I'm kind of curious why they are not getting much attention from the community.

Have you heard of https://mun-lang.org/ ?

It's an embeddable scripting language with the goal of being a Rust-like language that supports hot reloading of functions AND data. To achieve the latter, it uses GC'ed memory such that memory can easily be mapped when the memory's type changes.

It's still in early development but maybe one day will serve your needs :)

In terms of pure Rust engines/frameworks it seems the overall "problem" is lack of scripting, at least from my perspective. Mun seemed extremely interesting, but since even the project itself says "don't use it" I guess it's not a real option, and considering the amount of time we spent on the GDScript/Rust integration I'm a little worried that rolling something more custom would be even less efficient.