rust-game-of-life VS cargo-generate

This project is the first one on my Rust path in which I had to set up a project from scratch. All my previous work either used an existing project or copied a provided template.

The book avoids both pitfalls as it follows the first pattern but provides optional problems at the end of each chapter. To avoid blocking the learner, each problem provides a general hint to lead learners to the solution. If you cannot (or do not want to) solve a specific problem, you can continue onto the next chapter anyway. Note that in the associated Git repository, each commit references either a standard copy-paste step or a problem to solve.

cargo-generate: Quickly create Rust projects by using existing Git repositories as templates.

This seems to have a lot of overlap with cargo generate. I'm curious if there are differences you're exploring in philosophy/UX/features/implementation/whatever?

cargo-generate to generate projects according to a template (see cargo-generate)

That must be the connector/payment processor integration template. That's not serde specific, it's cargo-generate.

Tools like yeoman, degit, and cargo generate kept me happy for years. They add basic templating capabilities to the standard git clone but they stop there. You’ll be hard pressed to find tools that go beyond setting up a directory structure.

We would like to simply the next step and use cargo-generate tool to create our Arduino project from a template. Somehow (please, do not ask me why) it requires Perl to compile, so we have to do:

How does backpack compare to [cargo generate](https://github.com/cargo-generate/cargo-generate)? I've been using that one until now, but I haven't used its more advanced features.

Currently, it has two built-in ones for `cargo new` and `cargo init` (--bin and --lib) and there are third-party tools like `cargo generate` which provide for more, but they haven't accepted anything into the main distribution yet.

https://github.com/cargo-generate/cargo-generate