> It doesn’t scale, is not maintainable
We came up with “Atomic CSS” at Yahoo! to reduce the size of our CSS and facilitate authoring CSS inside a large codebase in a multi-teams environment. At the end of the day, we shaved close to 50% of our CSS and allowed different teams to create components without the need to namespace anything. So yeah, it does **scale** and it is **maintainable** (we achieve this easily via http://acss.io).