4 ms·
That is one of the reasons—you can view the slides also at https://speakerdeck.com/mdo/at-mdo-ular-css https://speakerdeck.com/mdo/at-mdo-ular-css if you don't
by mdo 12y ago
That is one of the reasons—you can view the slides also at https://speakerdeck.com/mdo/at-mdo-ular-css https://speakerdeck.com/mdo/at-mdo-ular-css if you don't want to watch the video.
I like to use prefixes and base classes. It's faster for browsers to paint, leads to fewer rules overall, reduces selectors, and helps prevent unnecessary overrides.
- oneeyedpigeon 12y agoMy aesthetic senses have always led me to a preference for button {} over .btn {}, class="foo bar" over class="foo-bar", etc. But I realise I'm in the minority and I need to get pragmatic. The slides have convinced me to check out the video tomorrow, which will be a start. codeguide.co also looks well worth checking out. At the risk of derailing the conversation further, what's the reason for leaving a trailing slash out of self-closing elements? I recognise it's optional, but including it gives you the option of XML-parsing your HTML; is there a non-aesthetic advantage?