Maybe useful someday

A short and efficient one

Because it's far easier to find code with the Search file feature of your code editor when it's in a descriptive filename (client.rs, email.rs, payments.rs...) than if everything is stashed in 10 different mod.rs or lib.rs files.

A thin HTTP API interface pattern.

This is what we often build in UIs with JS to interface with backends.

A faster implementation of the rust datetime library

A rust example project using SQLx and sqlite.

Read the pp_dataserver later to learn how to use Axum with a SQLite database.

A lightweight version of the builder pattern

anyhow works well.

A lot of confusion around unwrap(), I think, comes from well meaning folks saying things like “don’t use unwrap(),” when what they actually mean is “don’t use panicking as an error handling strategy.”

Of course, when possible, pushing runtime invariants to compile-time invariants is generally preferred. Then one doesn’t have to worry about unwrap() or assert! or anything else. The invariant is maintained by virtue of the program compiling. Rust is exceptionally well suited to pushing a lot of runtime invariants to compile-time invariants. Indeed, its entire mechanism of maintaining memory safety depends crucially on it.

A lightweight version of the heavy clap

Crates relying on a lot of crates are potential security flaws

An alternative to nginx. Is it needed though? Maybe I don't know much and my use cases of nginx are pretty limited. Let's see!

An awesome guide about the newtypes pattern. Great writing btw!

The name LOL.

volkswagen detects when your tests are executed in a CI-environment and makes them pass.

For educational purposes

A great example of how rust shines and how to use it.