The Future of Web Typography

Alex

Interact with us @crazyleaf. More from us → forpixels.com (graphic design blog), zabox.net (promote your design stuff) and weselldesign.com (design shop).

You may also like...

  • http://twitter.com/juanalzaga Juan Gomez Alzaga

    I will always think CSS3 / FontSquirrel is the best, the browsers will render everything better in some time. 

  • http://twitter.com/AndyM23 Andy M

    I agree Juan, CSS3 is my prefered method too, but there is a certain element of knowing the audience and their browser preference (maybe by default) and lack of updating. But again, there is a (relatively) limited amount of fonts available on FontSquirrel.

  • Anonymous

    I don’t think users not having Javascript installed is as much of an issue as it once was, Javascript is heavily relied upon by almost all major web app, think gmail etc. Also as long as the designer includes fallback typefaces in the case of no Javascript its not a complete disaster as only a small minority of users will be affected.

  • http://www.heatedtowelrailsoutlet.co.uk/ Heated Towel Rails

    Really good and nice info to all

  • Imraan Afridi

    Very good tips and so creative , thanks a lot for sharing such a useful tips.

  • http://twitter.com/AndyM23 Andy M

    I agree, it’s less of an issue in this day and age, but the main factor that puts me off using JavaScript based fonts is the load time, whilst still much less an issue than in previous years, there is still a noticable difference between one using a CDN or fonts hosted locally and that of JavaScript.

  • http://www.webdesign.nl/ Gerwin van der Feijst

    At our office we take the speed aspect very serious. This is the reason why we use Google fonts more and more. Starting out with SIFFR and Cufon that is a big improvement. No longer rendering text as images and distribution using a CDN .. will it get any better?