MCHPRS VS crates.io

You can compile redstone using Rust though, see https://github.com/MCHPR/MCHPRS and https://youtu.be/-BP7DhHTU-I

Someone made a Redstone JIT compiler.

I don't know if you know about MCHPRS. It's a multi-threaded self-hosted MC Server made specifically for redstone. It gives you more control over redstone.

https://github.com/MCHPR/MCHPRS (redstone only)

It sure is! https://github.com/MCHPR/MCHPRS

The relevant bit is https://github.com/MCHPR/MCHPRS and Rust snippet starting from 0:25

Pretty cool.

The program itself was written in an existing intermediate language called URCL, which was then compiled to CHUNGUS2 assembly. CHUNGUS2 is the processor made with Minecraft's redstone mechanics. The processor was emulated for development, but the demo is running on MCHPRS, a Minecraft server that uses Wasmtime's Cranelift to JIT the redstone operations, which are represented as a weighted directed graph. Before MCHPRS optimizing redstone performance using compiler techniques was not thought to be possible. With MCHPRS the demo takes 9 hours to run, it would take decades without it.

https://github.com/sammyuri/minecraft

https://github.com/MCHPR/MCHPRS

Yes, the 2,000,000x slowdown mentioned in the trailer is relative to vanilla. But because it would take a decade to record this footage at that speed, they're using this Minecraft server implementation optimized for redstone: https://github.com/MCHPR/MCHPRS

It looks like these are the only existing items, which were enough to accomplish the goals of this project

Rust has a rich ecosystem of frameworks and libraries that let you read, parse, and manipulate text files, interact with cloud services and databases, and perform any other job that your project's development workflow may require. And because of its strong typing and tight memory management, you are much less likely to write programs that behave unexpectedly in production.

All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.

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.