Most of the "a lot to love" points are also hit by BEM/SMACSS. In regard to this point: >You never have to deal with one instance of a thing needing a slightly

Most of the "a lot to love" points are also hit by BEM/SMACSS. In regard to this point: >You never have to deal with one instance of a thing needing a slightly different style than the other instances, which screws up your reusable classes. ...what I found was that just as often, I'd need a new Atomic class different in a subtle way from existing ones, and this was annoying to implement because a) it expands the kludge-dictionary of short class names you have to memorize, but often in a way that's too situational for anyone to actually memorize it, meaning the next time someone runs into the same problem they will re-invent the same solution rather than reread the entire list of Atomic classes to see if one exists, and b) the whole point of Atomic is that I shouldn't have to be writing CSS, and I was, all the time.