[adamkittelson]

I'm usually the last person to jump to the defense of anything golang related... but people seem to be raising eyebrows about the nodejs dependency. Assuming they're using it for asset compilation etc I really don't see the problem. There's no reason to keep rewriting that stuff in every language.

[jalfresi]

You don't see a problem with installing nodes for assets compilation? What is the tech world coming to...

[jerf]

I very much want to avoid ever programming in Node, but if the best asset management tools are written in it, and I don't have to program in it, so what? There's all kinds of code on my systems written in languages or frameworks or styles that don't want to have to write in myself, but, well, I don't. I just use them.

[0xCMP]

Typically assets involve more than just image and css files esp for any project you're building a full server for (i.e. not done with a static site generator), so yes that makes things more complicated, but their job is to remove the boilerplate from development (i.e. provide a "framework" to develop in) so you can do your existing development more easily in new projects.

And if you already have a better solution, or your solution requires an even more complicated set of tooling, just add `--no-gulp` and it won't bother you.

[CharlesW]

Sincere question: Assuming you're somehow doing web development without it, what is the problem?