Loading video...

Video Failed to Load

Go Home

Facepunch is attempting to reduce Load Times for #Rust, this is a quick test comparing Regular Rust vs current attempts on Staging Branch. The reductions are significant, Huge Work in Progress.

16,769 views • 1 year ago •via X (Twitter)

11 Comments

Chrysalis's profile picture
Chrysalis1 year ago

this is gonna be huge with the seismic alarm, will be much easier to defend offlines

Mobile Scanner's profile picture
Mobile Scanner1 year ago

Scan any documents, convert images into text, PDF files, etc. 👍

DB's profile picture
DB1 year ago

Your telling me I can die to nakeds faster then ever before? No way

Drummer Jacob's profile picture
Drummer Jacob1 year ago

I cant help but think that many of these fixes theyre doing to the game should have happened a decade ago.

fluctuoso's profile picture
fluctuoso1 year ago

Whaaaaaaatthefk

micay's profile picture
micay1 year ago

THIS is absolutely insane

Snowy's profile picture
Snowy1 year ago

HOLY W! I am glad they're doing more Performance updates.

DevilishTay's profile picture
DevilishTay1 year ago

nice now cheaters can join the game even faster

MADDCRACK's profile picture
MADDCRACK1 year ago

Load times are cool but they gotta do something about over all performance. Since the jungle update the stutters have been insane.

DrEarss's profile picture
DrEarss1 year ago

Now I can actually use the rust plus alarm to defend the raid and not watch it happen

20K.GG's profile picture
20K.GG1 year ago

Staging’s new async-loading build already feels way snappier. Facepunch usually lets big engine tweaks cook on staging until the next force wipe, so with this dropping mid-July the natural window is the August wipe.

Related Videos

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.

Gergely Orosz

51,776 views • 2 months ago