3 ms·
> I would have to first install Node You mean, locally, on your machine? But it's not a big deal. Not even a small deal. It's, like, not a deal at all. But I
by azangru 8y ago
> I would have to first install Node
You mean, locally, on your machine? But it's not a big deal. Not even a small deal. It's, like, not a deal at all.
But I get your point. I thought you were advocating a general approach, but instead you were describing your specific setup.
- kbenson 8y ago> You mean, locally, on your machine? Well, in this case development is done through Vim on the remote server, first in a dev environment branch, and then pulled from production. It would require installing the tool chain on the server, which is an artifact of my development process, but nevertheless should require consideration in my case. But yeah, I'm just describing my setup, and the ease of which it allows getting started and productive. I'm wasn't really advocating for or against using a build process for the front end in general, just noting my current process. I imagine if I was using a lot of modules in my front-end, I would see the benefit of putting more tooling in place to maintain and manage it fairly quickly.
- fencepost 8y agoBut it's not a big deal. Not even a small deal. It's, like, not a deal at all. I can't help but feel that the road to maintenance hell is scaled with tiny tiny things.
- azangru 8y agoBut from the maintenance standpoint, a package manager together with some bundling tool is so much more desirable than hand-copying links to scripts!