[JCB_K]

No it doesn't really, it keeps your HTML clean. Sure, there's better ways of getting a MacBook into your webpage, but this definitely shows the power of the :before and :after selectors.

[fredley]

It may keep your HTML clean, but it makes your CSS messy!

[JCB_K]

That's why I said there's better ways of getting a MacBook into your webpage. But my point still stands, :before and :after are very powerful.

[MatthewPhillips]

I'd much rather have clean, reusable HTML. CSS you can use preprocessors to abstract away the messiness.

[lolsal]

Aren't you using templates and macros for HTML already?

[Groxx]

Changing how the HTML macros expand likely ends up requiring CSS changes (in practice, though not necessarily in a theoretically-ideal code base). One change in two places, vs one change in one place.

[MatthewPhillips]

No, I typically write entirely client side applications.

[tobyjsullivan]

Any reading recommendations for someone who isn't?

[arnarbi]

> No it doesn't really, it keeps your HTML clean.

You can also keep your kitchen clean by stuffing all the dirty stuff into the cupboards.