A blog you can type into

Most technical writing about a language asks you to leave it. You read a snippet, nod, and then — if you are conscientious — open a separate tab, paste the code somewhere, and find out whether it actually compiles. That context switch is where most of the learning quietly leaks away.

So this site has a playground attached to it. Press any printable key, right now, anywhere on this page. The sidebar opens, the editor takes focus, and the character you typed is already sitting inside main. No button to hunt for.

The smallest possible hello#

fn main() {
    println!("hello");
}

That runs on play.rust-lang.org, the same service that backs the online Rust Book. There is no backend here — this site is a pile of static files on a CDN, and your code goes straight from your browser to the playground’s public API.

Why the trigger is a keystroke#

The header has a [playground] link, because discoverability matters and not everyone guesses that a blog will respond to typing. But the keystroke is the real interface. It costs nothing to reach for, and it means the distance between “I wonder if that works” and a running program is a single character.

The tradeoff is that every printable key is now spoken for. That is why the theme toggle is a link rather than a shortcut: d belongs to the editor.

What it does not do#

No crates beyond the standard library. No multi-file projects. No saving to a gist. If you want those, the real playground is one click away and does all of them better. This one exists for the thirty-second experiment — the kind you would otherwise skip.