Re:JavaScript Gom Jabbar
by jackson1442 on Monday July 03, 2023 @07:18AM
(#36571368)
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.
[ Parent
| on HN ]
Re:JavaScript Gom Jabbar
by petesergeant on Monday July 03, 2023 @01:33PM
(#36576289)
That’s interesting, might give that a whirl, thanks
Re:JavaScript Gom Jabbar
by jiggawatts on Monday July 03, 2023 @08:42PM
(#36580715)
I love watching people reinvent Visual Studio or IntelliJ IDEA, badly.
Re:JavaScript Gom Jabbar
by petesergeant on Tuesday July 04, 2023 @11:19AM
(#36587829)
What does this comment mean?
Re:JavaScript Gom Jabbar
by jiggawatts on Tuesday July 04, 2023 @07:34PM
(#36593844)
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.
Re:JavaScript Gom Jabbar
by jackson1442 on Wednesday July 05, 2023 @04:44AM
(#36597569)
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.