A battle between two methods of real typography on the web is starting. There are significant differences between them, ones that spell out a clear winner in the technical-sense. Yes, .webfont is more preferable than Typekit: it’s not controlled by a one entity, is file-agnostic, and has the backing of many of the top font foundries. That being said, it’s still basically a pipe dream:

As I understand it, the real difference between Typekit and the .webfont proposal is that .webfont, while it seems a very good and open solution, will need browser maker support in order to work. Typekit could theoretically work right now.

Typekit will obscure fonts so they’re difficult to steal; .webfont requires that “illegal use” conditions be built into future versions of web browsers.

The first one’s to market with a great product win—by the time .webfont gains any traction with browser makers, the fight will already be over.

✖