Prefix or Posthack

Eric Meyer, in praise of browser prefixes such as -webkit:

If the history of web standards has shown us anything, it’s that hacks will be necessary. By front-loading the hacks using vendor prefixes and enshrining them in the standards process, we can actually fix some of the potential problems with the process and possibly accelerate CSS development.

I’d add that vendor prefixes work very well with a steady diet of progressive enhancement. You, as a developer, are not bound by law to make every element on every page look exactly the same in every browser. The less tied-down each of us are, the faster all of us can move.

Introducing Typekit

A platform for css3’s @font-face. The real test of this will be how many hoops you have to jump through to embed a font, and how it handles failure:

We’ve built a technology platform that lets us to host both free and commercial fonts in a way that is incredibly fast, smoothes out differences in how browsers handle type, and offers the level of protection that type designers need without resorting to annoying and ineffective DRM.

The upside is that having a central place to access these fonts will be great for caching.

Tal Leming on Embedded Web Fonts

A rare take on embedded web fonts from someone who actually makes fonts and sells them for a living. He suggests a DRM system using a “root table” that says what fonts can be used on what domains, but then says this:

There is nothing that can be done about this. All we can do is present a person with a fork in the road. The person can license the font to give the designer the respect he/she deserves for creating something that the person likes and wants to use. Or, they can ignore the Golden Rule and hack the font.

If that’s the case, and he knows it’s the case, then why not forget the DRM entirely? Why not trust people to do the right thing from the start, and call them out on it when they don’t?