4 ms·
These are all improvements, I'm sure, but I'm less convinced they help address the problem I've most often confronted with on large projects, which is roughly t
by benohear 15y ago
These are all improvements, I'm sure, but I'm less convinced they help address the problem I've most often confronted with on large projects, which is roughly this: You need to make a change to a specific item because it looks crap on a specific screen. Do you:
a) Special case it, thus adding to the bloat and making it tougher to use elsewhere.
b) Change the general case, but then need to spend a lot of time going through the app to make sure this hasn't blown up elsewhere.
c) Create a new general case, which adds bloat and might never be reused.
Compounding the problem is that often the CSS is third party. For example you find yourself overriding this or that Jquery component, but then it turns out that the style you overrode is actually used in a completely different component.
- snookca 15y agoRead through smacss.com, if you haven't already. It advocates a modular approach that should minimize the impact that components have on other components, thus a style change to one component won't blow up the rest of the site. Third party tools can be hit and miss. Hopefully you're working with plugins/libraries that don't inject inline code and rely on namespaced classes to achieve the result you need. Then, you have control of the CSS to style as you wish. (disclaimer: I wrote smacss (but didn't write the blog post))