Oh, if only that worked in practice

> This is why no one has successfully done a major game on Rust. The foundations are too weak to support it. That's patently false. https://veloren.net/ People have made games in it. And in Zig, and C, and C++ and so. And assembly. And machine code. Unsafety isn't a problem it's lack of libs and integration. If you refer to AAA the issue is lack of engines where Rust is a must. I.e. network effect, you need engines in Rust to make games in Rust. And to make engines in Rust, more games need to require Rust.

> This is why no one has successfully done a major game on Rust. The foundations are too weak to support it. The Finals open beta is happening on the 6th. Check it out https://www.reachthefinals.com/ Here is a blog post about their usage of Rust: https://medium.com/embarkstudios/inside-rust-at-embark-b82c0...

I might have misunderstood what you've written, but is there a reason you can't use https://github.com/etemesi254/zune-image as a JPEG decoder? It has minimal use of unsafe and is performant.

I don't want to trivialize anything but I most of my time in gamedev was dealing with similar either engine uplevel-integration hell(the team I was on still has scars from having to rebaseline UE3 on a 3 month cadence which took... 3 months every time we did it so it was back-to-back uplevels) or dealing with these sorts of things even in established engines. Yes Unity does better but there's a ton of momentum with established commercial engines that have tens of millions of dollars invested in them. It was only recently that Godot has started making some inroads on the indie side of the engine space.

Your story points out the unfortunate corollary of the OP's point. He states that if there is unsafe code that is called, it's never the caller's fault. Conversely, it means the caller can't do anything about it, and must wait for an upstream fix.