…is a good idea, I’m telling you.
I’ve created this page to attempt to convince you. It shows examples and lists six reasons why it’s a good idea and three common arguments against them (some of which I refute).
Don’t need convincing? Here’s roundup of them from simurai.
I just added “The Big Three” sharing buttons to articles on this site: Twitter, Google Plus, and Facebook. I’ve shared my thoughts on sharing buttons like this in the past. I essentially decided that I didn’t like them for this site. So before anybody skewers me for hypocrisy, I thought I’d go back through my old thoughts and refute myself.
I needed some tooltips for a thing. In looking around for a little inspiration, I didn’t have to go further than my dock
November 30th, 2011 is Blue Beanie Day. It’s a (quite literal) hat tip to Jeffrey Zeldman, his book Designing with Web Standards, and a show of support for web standards.
I regret to say that I’ve never participated in this before. But I’m totally in this year, and I’ll tell you why.
Tab Atkins (Twitter) is a member of the CSS working group and contributor to several other working groups in the W3C. He works for Google on the Google Chrome Team. Browsers and specs are the bones and blood of our industry so that makes Tab, uhm, a orthopedic surgeon, or something. I ask Tab about all that stuff, and more, below.
In which I take a real example of somewhere I knew using sprites would be a good idea, create the sprite by hand in Photoshop (my preferred method), and then use SpriteCow to help with the exact position values needed to use the individual images. Pseudo elements are also used to help maintain accessibility.
Links from the video:
Kevin Dees interviewed me. We talked about all kinds of front-endy stuff, this site, and other fun stuff. (video)
Henri Sivonen:
I think vendor prefixes are hurting the Web. They are hurting Web authors. They are hurting users of browsers. They are hurting competition in the Web browser space.
I'm tempted to raise my fist in disagreement, but you know what, I'm not an oracle. I can't know the future nor know how the world would have turned out if we never used vendor prefixes.
Here's a guess though: if we were to go back in time and influence the decision such that browsers agreed to never use vendor prefixes, we would be worse off. Less browser innovation, less of the spec implemented, and more serious cross-browser problems when some browsers jump the gun and implement specs prematurely.
Vendor prefixes, while being an eyesore and requiring maintenance, have saved us from a dystopian present (maybe).
Bret Victor:
Now, take out your favorite Magical And Revolutionary Technology Device. Use it for a bit.
What did you feel? Did it feel glassy? Did it have no connection whatsoever with the task you were performing?
