[GilbertErik]

Sorry to nag, but I haven't yet brought myself to make it past the first paragraph. Maybe it looks elegant or classy on someone else's screen, but I had to go re-enable Evernote Clearly just to be able to read it. Am I the only one?

[sophacles]

Sorry to rant, but I haven't yet brought myself to understand this position. Maybe it makes sense to designers or snobs but I have go calm down for a while just be able to reply. Am I the only person who thinks that ignoring good content to complain about formatting choices is vacuous at best?

[Wilya]

We need a "hide comments complaining about font" userscript.

Seriously, it's the third perfectly fine article I read today where a quite high voted comment (with tons of children comments) is "I hate to be that guy, but your text has bad kerning on [some precise browser version].

(on the other hand, this one might be justified. Just checked on Chrome, and all the 't's miss their bars. It might qualify as unreadable. My (and your) point still stands for 99% of the other such complaints, though)

[swanson]

Take a look at some of the screencaps below (or mine here: http://i.imgur.com/XpVhDMx.png Chrome/Win7) - this isn't the typical "omg don't use dark gray on light gray". The "t" and "l" are in distinguishable, so it is pretty hard for me to actually read.

I'm sure it looks fine in the authors browser/OS of choice, but it is not usable in mine - regardless of the merits of the content.

[Wilduck]

> Am I the only person who thinks that ignoring good content to complain about formatting choices is vacuous at best?

No, you're not. I would much rather read high quality discussion about the content at hand. However, I'm reading using Chrome on Windows 7, and I literally had to open the developer console and change the font to be able to read the article. Like others have mentioned, it wasn't just hard to read, some of the characters were actually indistinguishable.

When readability gets that bad, I think it make sense for the topic to show up in these comment threads. Maybe someone will be around to fix the issue. Maybe others will learn about what happens when you don't test a site in different browsers.

[jarrighi]

It is good to be alerted that the font isn't rendering properly on Windows Chrome, though. I think most of the PyLadies who use Chrome are on Mac or Linux, and the current design of the site is relatively new. Now we know we need to fix this.

[threedaymonk]

There probably ought to be some general principle of web design here: don't get fancy with stuff you can't support. If you don't have a wide range of devices for browser testing, that's OK: just stick to the standard fonts that work everywhere. If you are going to get fancy, do it right, and test exhaustively.

I know everyone opts for fancy, though!

[parsnips]

yes, probably.

[krelian]

Chrome's Windows font rendering rears it's ugly head again. While the fault here is entirely with Chrome I still don't understand how so many people (and even some high profile projects/organizations) choose to use those web fonts which are unreadable in Chrome.

[Jenk]

http://i.imgur.com/XcqHLyE.png

Was about to post the same complaint :)

[DoggettCK]

The content of the article was great, but I had to remove the font-family style from the body tag with Firebug due to the way Firefox was handling aliasing on the font.

Aside from that minor nitpick, I learned something new and valuable, so it's worth reading if you don't already know about git rebase.

[throwawayG9]

I only use Firefox and Liferea (when I find a good RSS to add), so I had to close this article because it was unreadable (I don't have other software to "fix" blogs, like the other commenters).

I don't see anything wrong with complaining about this. It's feedback for the author. Would you not complain if someone posted an invisible article, to which you need to apply some trick to make it appear? Would you not want to know why potential readers/subscribers are bouncing?

Another thing I usually hate in these blogs: small fonts. But at least I can just do ctrl+, so I never complain about that. But still hate it.

[GilbertErik]

https://docs.google.com/file/d/0B_sHgQoVOruvTmJjdHlWUTk4dGM/...

Ya know what. It looks fine in Firefox, but that font looks like garbage rendered in Chrome. I don't know if it's the font-family or the font-size, but something's making me want to scratch my eyes out or make me want to kill my screen with fire.

It's probably an unfair generalization to assume that all female Python developers don't use Chrome.

[MBCook]

Wow. I'm on Safari in OS X and it doesn't look anything like that. No wonder you guys are having trouble reading it.

http://imgur.com/TAQBRcV

I'd rather it just be left at default, but at least it's readable.

[rb12345]

Could this be a Windows-only issue? I found that it was unreadable on Firefox 19, Opera 12.02 and Chrome on Windows 7.

[mimiflynn]

You're right, it is unfair to generalize that all female Python developers don't use Chrome. Wonder if it looks better on a Mac in Chrome; it looks terrible in Chrome on Windows.

[GilbertErik]

It's a shame because Quicksand looks like a great Sans Serif font. I hope that the immediate repulsion I felt when I opened this article doesn't detract from people reading the great gentle introduction to using rebase.

[DanBC]

It's just a normal unreadable article in Chrome on OSX. On Chrome on Windows something's broken.

[ineedtosleep]

Chrome and thin fonts don't mix well. That said, I still don't understand why people use thin fonts for body copy. It reduces readability so much (even on FF where the rendering is fine).

[jakub_g]

Curiously for me it's garbage in Firefox 19 and normal (except kind of gray-on-gray) in Opera 12 and Chrome 25.

[kevinthew]

Completely garbage to me as well. Chrome 25 on Windows. Looks like hieroglyphs.

[lloeki]

Here the glyphs are rendered fine, but the kerning is really bad.

[mimiflynn]

Same here, can barely read it so I sent it to Pocket to read later.

[nightpool]

Not just Chrome: It's pretty terrible on older Firefoxes too. Firefox 16 here, and while it's not as bad as Chrome, its not very great either.

[lucian1900]

Indeed. Completely unreadable on both Chrome and Firefox, on Ubuntu. Had to use ireader.

[corresation]

Chrome 25 on Windows here and the same problem -- the font has extraordinarily poor hinting (or Chrome is malfunctioning), leading to critical elements of the text being discarded at that size.