• # November 10, 2011 at 1:41 pm

    I’ve been using Google fonts in PS for over a year. I haven’t have the need for any fonts in many months. I went back a couple months ago and noticed they vastly increased their library and it is still continuing to grow…

    Since we are on the subject though…

    When you guys use them, do you externally link them, @import, embed the fonts, or ??

    I have always used the @import method, but after recently reading an article on page loading times, it mentioned that the @import (in general, not specific to Google fonts) method drastically decreases page load speed. Any thoughts?

    # November 10, 2011 at 3:48 pm

    I just add them to my main stylesheet. I haven’t used @import nor have I found a reason to.

    # November 10, 2011 at 4:19 pm

    @standuncan Using @import effects your page load time minimally. That being said, I generally don’t use it.

    # November 10, 2011 at 4:25 pm

    Thanks @ChristopherBurton and @joshuanhibbert, I appreciate your guys’ input.

    # September 6, 2012 at 2:43 am

    i like Google Web Fonts and i dont know more about Typekit, but google web fonts is providing few fonts which we have.

    # September 6, 2012 at 7:33 am

    @RaviDesai At the same time, most people can’t tell the difference between a good typeface from a bad one. And within the Google web font library, there are few that actually render well on screen. Google pays a very low amount to the Type Designer’s that submit to their library so perhaps that is why we’re seeing low standards. And as Matthew Butterick said, “Google Web Fonts aren’t really open source”.

    Typekit on the other hand at least cares about their product quality over product quantity. They make sure the fonts are hinted and render properly. Whether it be from the foundry or by doing it themselves. Typekit isn’t perfect either but at least they’re trying.

    I’ll be writing an article in a few months with another advocate for type designers and I’ll drop a link in this thread when it’s out.

    # October 8, 2012 at 2:51 pm

    I like google webfonts because its FREE ;-)

    # December 1, 2012 at 1:29 pm

    Google Web Fonts are great, I use them all the time.

    You just don’t want to go crazy adding to many of them on a site, or you will increase your load times.

    # December 1, 2012 at 6:59 pm

    In all fairness, Typekit selection is vastly superior. Some of the best fonts ever designed are on Typekit: FF Scala, FF Absara, FF Meta, Adobe Minion, Futura, Gill Sans, and other masterful creations. You just don’t get this plateau of quality with Google fonts.

    Having said that, I would not subscribe to Typekit. They merely provide a service, i. e., you don’t get to keep the fonts. I’d rather pay a bit more upfront but get them fonts for life.

    Slightly OT, I’m unsure about the technicalities so I’d like some clearing up:

    – Do Typekit and Google Fonts resort to the same font loading method?
    – Are there drawbacks to setting up a subfolder with your fonts of choice and referring to it via the @font-face declaration vs scripting and other methods?

    # December 3, 2012 at 3:29 am

    I have used Google Fonts in the past, but now use TypeKit as you get their best package included in Adobe Creative Cloud.

    TypeKit’s selection is infinately better, but for a 100% free service, Google is really good and does have a few gems.

    Another advantage with both is a high quality set of scripts to get them working. @import still isn’t totally relaible, so to have methods developed and tested by the likes of Adobe and Google is a plus point.

    # December 3, 2012 at 8:40 am

    @alanshortis ,

    What are the differences/advantages/disadvantages of using @import vs. @font-face?

    # December 3, 2012 at 7:18 pm

    Typekit uses encrypted @font-face which you can see within web inspector. Typekit and GWF use the same loading technology.

    Are you guys talking about using @import to import another stylesheet such as typography.css?

    # February 28, 2013 at 7:50 am


    > Having said that, I would not subscribe to Typekit. They merely provide a service, i. e., you don’t get to keep the fonts. I’d rather pay a bit more upfront but get them fonts for life.

    Unfortunately that’s not possible. Adobe explicitly forbids embedding .ttf/.otf files of Adobe fonts directly into a webpage in their EULA. That’s kind of the whole point of Typekit (and WebINK etc): to use Adobe fonts on the web.

    # February 28, 2013 at 8:24 am

    This reply has been reported for inappropriate content.

    While you’ve bumped this topic anyway, I’m using Ubuntu form Google Web Fonts. Typekit also has Ubuntu. Does that make Ubuntu one of the ‘few gems’ Google Web Fonts has? :P

    # February 28, 2013 at 12:51 pm

    Using google you can host them on your site and call them via @font-face correct???

Viewing 15 posts - 16 through 30 (of 81 total)

You must be logged in to reply to this topic.