[Archit3ch]

In some cases the ergonomics are worse than C, which is a feat in 2026.

Portable SIMD is (perma?) nightly.

Requires 'unsafe' everywhere.

To skip bounds-checking, you typically need to switch your writing style from loops to iterators.

No JIT, so you need multiversioning and/or target-cpu=native. Since Rust doesn't bring a compiler, you need to predict all your target architectures in advance.

Cannot inspect @code_llvm/@code_native at the function level like Julia, you need to compile the entire app.

Prioritizes Floating-Point strictness over --ffast-math. It's a genuine win for safety, but that's overkill in some domains (e.g. graphics, games, audio).

[sgt]

Yes seems like too much work or hassle. I'm kinda looking at Java as a Rust replacement, and Zig as a C replacement. This might just be the ultimate combo.