Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Fonts Redesigned

fonts.google.com

Post reply on HN
Print view View original

71–80 of 268 posts

Re: Google Fonts Redesigned

#71

Post by mrweasel »

ocdtrekkie wrote: post #43

"Your browser is not currently supported. Google Fonts works best on Chrome, Firefox, or Safari." Google still treating Edge users like trash, I see[0]. Microsoft Edge works fine for the vast majority of websites, and a block like this telling you to get a different browser is incredibly painful. If you tell me I need a different browser, I'm going to find a different company or website to do business with. [0]Gmail…

More and more sites are only tested in Chrome. It's not just Edge that no one cares about, Firefox is becoming a second class browser as well.

Often it's pretty obvious that the authors didn't even try Firefox, because the JavaScript isn't even loading properly.

Re: Google Fonts Redesigned

#73

Post by laumars »

SEMW wrote: post #4

Looks great in Chrome, completely broken in Firefox: https://i.imgur.com/XRMgcHp.png .

I get the same in every browser I try on Linux.

I don't get the point of this. I really don't. While far from perfect, web fonts have largely been a solved problem for a while now, so why are Google reinventing this wheel? This seems to happen all the time with the web; people taking old ideas and reinventing them again and again, in yet more bloated ways, breaking things for millions.

Re: Google Fonts Redesigned

#74

Post by magicalist »

michaelmrose wrote: post #70
mortenjorck wrote: post #12

This is a gorgeous redesign that really lets the typography shine, as well as deftly addressing numerous usability issues with the old site. The family size filter in particular makes finding a usable set of weights much easier, and the featured section adds a welcome new layer of curation. Two minor observations: - It would be a great addition to the family size slider to be able to filter for "contains italics." So…

Are you using chrome? It looks pretty dumb in firefox. It looks like this. http://imgur.com/IT7x83h

Chrome and Firefox look exactly the same to me

edit: from your comment below, maybe you're on Linux? Sounds like you're seeing the same thing as this subthread: https://news.ycombinator.com/item?id=11903444

Re: Google Fonts Redesigned

#75

Post by plgs »

ocdtrekkie wrote: post #43

"Your browser is not currently supported. Google Fonts works best on Chrome, Firefox, or Safari." Google still treating Edge users like trash, I see[0]. Microsoft Edge works fine for the vast majority of websites, and a block like this telling you to get a different browser is incredibly painful. If you tell me I need a different browser, I'm going to find a different company or website to do business with. [0]Gmail…

Google Inbox is also blocked on Edge, which is sad. I wonder why they're blocking it. As you said, Edge works fine with most websites, it's not IE6...

Re: Google Fonts Redesigned

#76

Post by gotchange »

I congratulate the Google Fonts team The redesign job looks gorgeous and elegant in terms of UI and UX too but can I make a few suggestions if possible?

1- Can you please add a double view button at the top to toggle between «List» and «Grid» views for maximum convenience?

2- At the risk of sounding a bit pedantic but some example sentences for the Arabic fonts don't look perfect.

For example, for the «Amiri» font, it's الظلال أخفت القمر or more naturally أخفت الظلال القمر and not الظلال أخفى القمر [1]. For «Lateef» and without going over a lot of MSA grammatical rules, this is the more correct version of the example sentence انطلق صوتُ مسجّل عبر مكبِّر الصوت المنصوب أعلى الباب. [2]

[1] The shades hid the moon.

[2] A recorded voice went off through a megaphone/speaker mounted above the door.

Re: Google Fonts Redesigned

#77

Post by icebraining »

mortenjorck wrote: post #19
di wrote: post #9

If anyone is curious about the sample text: * "All their equipment and instruments are alive." (Mr. Spaceship, by Philip K. Dick) * "A red flair silhouetted the jagged edge of a wing." (The Jewels of Aptor, by Samuel R. Delany) * "I watched the storm, so beautiful yet terrific." (Frankenstein, by Mary Shelley) * "Almost before we knew it, we had left the ground." (A Trip to Venus, by John Munro) * "A shining crescent…

The first one on the list had convinced me this was a very interestingly-trained Markov chain generator. I need to read more Philip K. Dick.

That's always an appropriate state of mind. And luckily, that story is already in the public domain: http://www.gutenberg.org/ebooks/32522

As are a few others: http://www.gutenberg.org/ebooks/author/33399

Re: Google Fonts Redesigned

#78

Post by huntleydavis »

Very impressive performance loading considering the number of fonts. Curious if they are just loading an incredibly stripped down version of each font for the preview and then lazy loading in the full font if you click to edit the text. Either way thumbs up.

Re: Google Fonts Redesigned

#79

Post by stonogo »

netinstructions wrote: post #45
stonogo wrote: post #32

Earlier quoted context omitted.

Pagination.

I found the non-paginated version to be very responsive and quick. Personally, I prefer non paginated results as long as they're quick, and some user testing studies indicate this as well[1]. UX folks seem to prefer not to paginate[2]. Who loves pagination? Usually advertisers. [1] https://webmasters.googleblog.com/2011/09/view-all-in-search... [2] http://ux.stackexchange.com/questions/21375/is-there-a-point... Codin…

Links from half a decade ago are irrelevant here. The claim that pagination only benefits advertisers is ironic, given we are discussing a Google page.

The point of pagination in this case is to reduce the client-side processing load and up-front bandwidth consumption to view the page. This isn't a news article. It's a set of nontrivial binary files being downloaded and rendered using javascript.

The OP of this thread complained that infinite scrolling plus lazy loading put his browser under heavy load. The first respondent accused him of wanting everything loading up front. I merely suggest a middle ground.

Re: Google Fonts Redesigned

#80

Post by michaelmrose »

icehawk219 wrote: post #51
Scarbutt wrote: post #16

Earlier quoted context omitted.

No one tests on firefox anymore, is sad how firefox is being ignored more and more everyday.

From my experience with front-end dev's it's not that they don't test in Firefox but rather they only test in Chrome. I've worked with FE devs who insisted it was unreasonable to expect them to test in all the major browsers.

Web devs as a group seem to be ridiculous. Note this doesn't mean everyone just a greater incidence of such.
Post reply on HN