Baker – language-agnostic project scaffolder with hooks (Rust)

Rust-made Baker promises quick project starters; fans hype, skeptics shout “another clone”

TLDR: Baker is a Rust-made tool that quickly spins up new projects with templates and optional hooks. The crowd is split: fans love the fast single-binary setup, while skeptics warn about hook security and “curl | sh” installs—still, curiosity wins as many plan to try it.

Baker, a new command-line tool written in Rust, promises to “bake” you a fresh project in seconds. It ships as a single download, asks a few friendly questions, fills in template files (.baker.j2 using the Jinja template language), and even runs optional hooks to automate the boring bits. The launch points to Baker on GitHub and the comments instantly turned into a bake‑off: half the crowd smelling warm bread, the other half yelling “carbs.”

The hype squad is loud: they love the fast, single‑binary setup (Homebrew/Scoop/one‑liner installs), the language‑agnostic templates, and the “no Python or Node needed” angle compared to tools like Cookiecutter and Yeoman (popular project starters). One fan said it felt like a “starter kit on turbo,” and the memes flowed: “I knead this,” “rise and shine,” and “hooked on hooks.” Teams dreaming of unified templates across languages were swapping “house recipes” before the dough even rose.

But the spice is real. Skeptics cry “yet another generator,” groan about YAML question files, and side‑eye piping installers (curl | sh panic, PowerShell jitters). Security hawks warn that template hooks can run scripts you didn’t write—cue “supply chain” alarms and calls for sandboxing and signed templates. Even nitpicks about symlink handling popped up. Verdict: excitement meets paranoia—classic dev drama—while everyone quietly downloads the binary “just to try it.”

Key Points

  • Baker is a Rust-based CLI tool for scaffolding new projects with language-agnostic hooks.
  • Precompiled binaries are available, with installation via Scoop (Windows), Homebrew (macOS), shell script (Linux/macOS), and PowerShell (Windows).
  • .baker.j2 files are templated (Jinja), filenames can be templated, and .bakerignore controls copied files.
  • baker.yaml defines template settings and interactive questions with templated help/defaults; JSON configs are also supported.
  • Advanced features include symlink handling, non-interactive mode, conditional questions, validations, built-in filters, customizable hooks, and platform variables.

Hottest takes

“It’s Cookiecutter without Python and I’m here for it” — yak_shaver
“Any tool that runs template hooks is a supply‑chain grenade” — secops_skeptic
“I knead this in CI; piping install scripts? Hard pass” — bread_pun_enthusiast
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.