Facepunch added several community-requested features that seem small but are gigantic for sanity:
This is the headline feature. Everyone knows the Minicopter and the Scrap Heli, but ocean travel has always been limited to the RHIB and Rowboat. Devblog 236 introduces the "Bathysphere" (unofficially dubbed "The Bubble" by the devs).
Rust 236 demonstrates steady, conservative evolution around async and concurrency. Rather than radical rewrites, the focus is on compatibility, performance improvements in executors, and clearer best practices. The ecosystem’s async story remains diverse (tokio, async-std, smol, etc.), and the language maintainers appear content to let the ecosystem sort the specialization tradeoffs.
Why it matters: Rust’s safety guarantees are compelling for concurrent systems, but fragmented async approaches can confuse newcomers. Continued pragmatic work — better docs, clearer patterns — will help cement a standard set of idioms without imposing one-size-fits-all choices.
Rust 236 nudges at dependency maintenance and crate quality: audit tooling, clearer guidance for crate authors, and nudges toward maintainability. This matters because Rust’s strength — a vast collection of small, focused crates — also introduces risk: outdated or unmaintained dependencies can become liabilities.
Takeaway: expect tooling and cultural efforts to favor maintainable crates, better metadata, and clearer signals about health and maintenance status.
This is the section that will make your graphics card either cheer or combust. Rust has been notoriously CPU-bound for years, but Devblog 236 shifts the load.
Key Performance Updates:
Warning: The devs note that the new occlusion culling can sometimes hide players behind rocks that aren't fully rendered at long distances. Expect a hotfix for "invisible players" in week two.