This. The whole comment feels like self-inflicted damage. We have a special repository for various template projects and when we need to create a new project we copy one from there. Sure, it's not bleeding edge, but also not legacy as we bump dependencies from time to time and sometimes replace tools with newer ones.

I admit, it would be nice to have something like Maven Archetype to have things a bit more formalized, but for most of the time a good old copy-paste works well enough.

If you wanted something extra fancy you could even set up a Yeoman generator that accepts input parameters and builds out the starter project based on those.

That’s interesting, might give that a whirl, thanks

I love watching people reinvent Visual Studio or IntelliJ IDEA, badly.

What does this comment mean?

Proper IDEs will set up a lot of the "new project" boilerplate for you, wire up compilers, linters, etc...

People still using text editors like EMACS or VI need to do this themselves, often through some random mish-mash of unique and special text templates, scripts, and copy-pasting from previous projects.

Then unironically they'll proudly proclaim to be productive because of all the tooling they've successfully set up over many days of effort.

The boilerplate is nice for “a vue project” but it starts to fail when you want “a vue+ts project that includes our internal components library, auth, terraform, uses tailwind, etc.” It doesn’t take long to set this up by hand, but automating it makes it less prone to human error - which would be harder to catch in CR because the changes will typically be massive.

But if you CR the Yeoman generator, every project’s initial commit can start from a known-good state since all you need to do is provide it the project name and location.