touche VS bacon

If you wish to keep it simple by staying away of async runtimes, I recommend my own thing that I built precisely for people that are learning Rust: https://github.com/reu/touche

Not really a guide, but I implemented this webserver library to teach Rust and HTTP concepts to my coworkers. It is (arguably) simple Rust code with minimal dependencies, so it may be useful for your studies: https://github.com/reu/touche

If you wish to checkout an alternative: https://github.com/reu/touche Ps: I am the author

Probably one of the biggest speed ups to your inner loop writing / running code is to use something like https://github.com/Canop/bacon/. I used a combination of the docs and GPT chats to increase my learning speed a lot.

Nice, I'll have a look. I miss having bacon in a tmux split, wish TS had something like that.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.

bacon + nvim-bacon

bacon

I love cargo-watch and still it use it situationally, but as a companion to my editor workflow I mostly switched to bacon. Being able to switch with one keystroke to another cargo subcommand is delightful.

Try bacon for checks & test!

Was it bacon perhaps?