use SASS/Less and rebuild the css. I don't know what the problem is with that ? ...

jasonkester · on Jan 4, 2019

Because that is a huge pain in the ass to set up.

I think front-end devs forget this part, because they always tend to have a giant complicated built tooling setup in place, so adding one more little thing seems easy.

But the default is to have no tooling whatsoever, so the thing you're proposing that you "don't know what the problem is with" is a process that has a step one that lies several steps before even "install Node on my dev machine".

I've gone through all that (specifically to change a color in bootstrap), and even now that I have it set up and runnable, I'd still use the grandparent's proposed $10/month web service if it existed.

Edit to add: ...and now that a sibling comment has pointed out the existence of bootstrap.build, I'll be signing up for a paid account.

philbarr · on Jan 4, 2019

> because they always tend to have a giant complicated built tooling setup in place

I know people must have their own setups that they use in GitHub somewhere. I have some, but I don't do lots of web dev and they're a bit shit.

Does anyone have any "default toolchains" in GitHub that they use to start new projects? Including SASS, webpack, common polyfills, etc.?