Web Fonts Future Looks Better

That was very interesting. Thanks for posting.

The EOT and the font face at thing sounds kind of exciting and considering IE was the one to create the EOT thing... it will have support for such thing, but the code to do it may be different then Mozilla's... which would mean more code for web designers/programmers.

PHP would be simple to use to solve it, but then, not every host supports PHP and not everyone knows PHP.

This may seem weird... maybe every other browser would go to EOT? I doubt IE would go away from EOT...

EOT is fine as long as there are free EOT converters.
I already use @font-face (with commercial fonts) on some personal use sites, and really don't see the issue.

The analogy of it compared to photos and office are very different.

Fonts like Photos:
You purchase a photo to use on your site from the photographer. There is absolutely NO way to prevent that photo from being captured by a viewer. You trust that they will not reuse your pics on your page, unless you make it downloadable.

Fonts like Office:
You buy Word and make a document out of it for your site. Unfortunately .docx isn't readable by web so it is downloaded on the client and they cannot open it, so either they buy it, or you link an executable to run it.

I can see fonts being like both examples. It is hard to decide.

Using @font-face doesn't prompt a dialog box that says "Install Segoe Print?" when you access a page like some of the articles declare.
So if people are wanting that font, are they going to check the CSS pages and get the source document? Why when googling torrent fonts and you get any you want.
Point: They are already "available" to people who are "techy" enough to try to get them off your site.

So I just read that @font-face doesnt work in I.E. is there a workaround for this... I hate to completely ignore Internet Explorer users...

Bah! They need to get smarter. But there is one... I just need to find it.