5 ms·
Neat. Now add a way to hierarchically roll-up these micro-classes into semantic classes behind the scenes (Perhaps in webkit?). Compile things so you only carr
by DanielBMarkham 8y ago
Neat.
Now add a way to hierarchically roll-up these micro-classes into semantic classes behind the scenes (Perhaps in webkit?). Compile things so you only carry-around the css micro-classes you've used, and make a flag to either deploy using the semantic or micro class method.
Best of both worlds. There are also some other mix-and-match ways of doing this. Where the real value is separating the tiny CSS adjustments you make from the business-class stuff, creating a middle tier (which this guy deploys directly)
It might make things easier. Or it could be yet another dumpster fire. I think it depends on how it's used.
- Flenser 8y agoYou could do this with SASS or LESS. Make all the "functional" classes as abstract mixins or placeholder selectors (in SASS parlance), and then use them to define your concrete semantic classes.
- Semaphor 8y agovariables and mixins, clean css, readable templates instead of some overloaded hodgepodge of classes.
- DanielBMarkham 8y agoYeah. I was reading this thinking "If only we had some way of abstractly creating CSS!" Which of course we already do. Maybe there's a case that the toolchain or conventions need tweaking. So it's worth the discussion in my mind. Most times you really don't realize what you need from a tool/framework until you've reinvented it, so we need folks like this doing sanity checks on where the rest of the industry is going.