twitter/bootstrap — comment on commit 5ad5dde1e24f668cf9b720dd59fc2a7d4808c0b3
File:  line 0
By inmarelibero:

Well I think that using the custom builder in a software house is quite hard, experiencing that in my office. Much time would be wasted if I had to set values, download a custom build, unzip, copy, see it doesn't fit well, set values, download a custom build, unzip, copy, try again, ok it works, then I'd like to try with other values, etc...

I suggest hardly to propose a platform customizable as much as possible through variables. Of course maintaining simplicity and usefulness.

I think it is reasonable to assume that less people will edit for example `mixins.less` than `variables.less`; I, as user, surely expect that changing values in `variables.less` everything works as expected, but it does not as is because 12 is fixed.

Adding support up to 24 is easy in my opinion, the PR I submitted works for me on real projects, and I was waiting for that to develop the responsive version. Users will be free to download a custom build AND to edit that on a already begun project. Personally I'd hate to be forced to download a custom build and put it on a project I didn't touch in months and having to hope things work with modifications I could have done on other files.

About the complexity of code and the extra output: this has no meaning imho; adding some lines doesn't affect comprehension and the gain would be great: the possibility to change things only by changing variables.