Live data from Hacker News

The Fastest Google Fonts

csswizardry.com

151–152 of 152 posts

Re: The Fastest Google Fonts

#151

Earlier quoted context omitted.

> P.S. Why the trailing slash on the tag? It’s completely useless, by definition, and trailing slashes can mislead people into thinking that you can close tags that way, which you can’t. Simple: so that XML parsers can load the HTML, as they are not aware of the HTML context which allows "unclosed" tags.

You wouldn’t parse an HTML document with regular expressions. So why would you parse one with an XML parser? It’s just wrong . (And an effort doomed to failure if you ever have to deal with documents other people wrote, because very few will parse.)

There are a lot of more XML parser than HTML5 parser in the world. That's an argument for polyglot markup, if you like the open web and HTML as an API.

Re: The Fastest Google Fonts

#152
post #11

Earlier quoted context omitted.

The main content may load quickly, at least with javascript disabled, and that's a good thing; but I can hardly read the text though. 300 weight text at 51% grey is awful. When I see pages formatted like this, I tend to make a decision between opening the inspector and fixing the fonts, or just not bothering to read it, since it's clearly not designed to be read. Original: https://qui.suis.je/drop/faster/illegible.pn…

Simply bumping the weight upto 400 would make the site much more readable.

About to release this fix now.
Post reply on HN