1. In Rust, this struct is 16 bytes (on x86_64, again) and in C, it is 24. This is because Rust is free to reorder the fields to optimize for size, while C is not.
2. Social factor: it is more convenient to write a bite more dangerous code than in the equivalent C. Firefox failed two times to parallelize Firefox's style layout twice. They get it right the third time with Rust. Does a junior write faster production code in Rust than in C?
3. Compile time vs runtime: Rust provides a bit of safety at runtime (index access)

If C is the fastest language, is there any inherent reason why Rust could not do the same things? At the fundamental level, the answer is “there’s no difference between the two.”

But projects does not work only on the fundamentals, "We’re usually talking about something in the context of engineering, a specific project, with specific developers, with specific time constraints, and so on. I think that there are so many variables that it is difficult to draw generalized conclusions."

Rust is a language for building foundational software. - https://smallcultfollowing.com/babysteps/blog/2025/03/10/rust-2025-intro/

What all clients have in common, however, is that the services they build with Rust are foundational to their core business. Rust is used for building platforms: systems which enable building other systems on top.

This mindset takes away the focus from Rust as a C++ replacement and also explains why so many teams which use languages like Python, TypeScript, and Kotlin are attracted to Rust.

What is less often talked about is that Rust is a language that enables people to move across domain boundaries: from embedded to cloud, from data science to developer tooling.

Rust serves as a catalyst: companies start using it for critical software but then, as they get more comfortable with the language, expand into using it in other areas of their business.

Magisk is a suite of open source software for customizing Android, supporting devices higher than Android 6.0.

The native part is written in Rust.

A joke about rust infrastructure. It becomes obsolete as time goes.

1. avoid uneccessary default features
2. use specialized lighter crates

I have the same idea for a node js backend serving a fancy UI :)

It would be better to split the UI and the server while developing to benefit from hot reloading.

Example: https://git.sr.ht/~pyrossh/rust-embed/tree/master/item/examples/axum-spa/main.rs

• relying on shared mutation
• treat the compiler as something trying to help
• ignoring proper module organization

You have to unlearn a few habits.

1. Writing Rust code like other languages
2. Neglecting the most important 20% of Rust. Trying to learn everything at once: you don't need to learn all at once. Focus on the 20% that gives the 80%.
3. Being a productive procrastinator: watch a video or read a blog post.
4. Thinking you can vibe code Rust like JS...

Hands on practice! The programmer has to internalize the concepts of Rust. Getting a grasp is not enough.

Replace the standard DefaultHasher to ahash::{AHashMap, AHashSet} to gain 18% improvements.

I don't understand some things here

• gen blocks: similar to python generators as far as I understand. They are lightweight compared to the classic Iterator pattern
• default field values (and avoid new() for it)
• inner structs
• never type
• try expressions

The ability to run scripts is also a great feature imho.

Create a type similar to another existing type :O

Some interesting statistics.

Rust interact with other parts of the codebase through

1. Rest API (56%)
2. Language interop (44%)
3. RPC (21%)
4. WebAssembly /WASI (19%)

Projects developed in Rust are:

1. CLI tools (40%)
2. Systems programming (38%)
3. Web development (35%)
4. Desktop / GUI applications (21%)
5. Network programming (17%)
6. Embedded / IoT (12%)
7. Academic /Scientific / Numeric (9%)
   and more games, databases, DevOps, Security, data science / ML / AI, Blockchain, ...

As for why: write safer code, build high-performance applications, iterest or fun, improve skills and career opportunities (stay competitive in the industry), handle concurrency or multithreading safely, ...

How to learn?

• official rust documentation (95%)
• books (32%)
• video or podcasts (19%)
• online courses (12%)
• University or academic coursework (5%)
  and employer-provided training, rust training companies, ...

In the meantime, it consumes 10 times more resources than the tool htop

A performance bounty program