There is a kernel of truth in there as I often wish CSS let arrange elements independent of the order they appear in the HTML doc. ...and that type of thing is

There is a kernel of truth in there as I often wish CSS let arrange elements independent of the order they appear in the HTML doc. ...and that type of thing is probably the source of most of the discomfort that the author feels with the way browser separation of duties happens, even if he didn't express it very well: as general-purpose view frameworks go, CSS is an extraordinarily shitty specimen, completely unsuitable for many tasks - every time you've ever had to alter a line of HTML to make your layout work correctly, you've been staring straight at the heart of what is wrong with CSS. Many things that should be handled exclusively within view code (and would be in a sane project) end up leaking into many other parts of the system. And that's even before you start dealing with browser incompatibilities. I'm not sure that there's any solution, though - yes, we all know it's a terrible setup, but none of us can do anything about it at this point, so we turn to libraries that try to shield us from the complexity. C'est la vie, this is what happens when things evolve naturally under changing needs over a long time...