6 ms·
I have had that issue starred for years, as I assume most of the others have. The failure of Chromium to support DirectWrite in a reasonable timeframe has kept
by bhauer 13y ago
I have had that issue starred for years, as I assume most of the others have. The failure of Chromium to support DirectWrite in a reasonable timeframe has kept me pure in my unwavering support of Firefox, even when Chrome was considered the hipper browser. It's easier now to remain with Mozilla, what with anti-Google sentiment becoming mainstream.
Jokes aside, it's embarrassing how long that issue has been left to rot. All fonts in Chrome-Windows look awful once one is used to Firefox or Internet Explorer's rendering.
- ygra 13y agoNot even when you're not used to the other browsers' font rendering. On some of Google's web pages the fonts are actually unreadable unless you scale the page to 250% or so.
- zw 13y agoSimilar type of deal with [going 64-bit](https://code.google.com/p/chromium/issues/detail?id=18323 https://code.google.com/p/chromium/issues/detail?id=18323) on Mac OS X. Has languished for multiple years. DirectWrite shipped in 2009, one month after Snow Leopard with 64-bit recommended for apps by default.
- cpeterso 13y agoPlus ASLR is much less effective with only a 32 bit address space. (Firefox on OS X is a 64 bit application.)
- at-fates-hands 13y ago>>>> All fonts in Chrome-Windows look awful once one is used to Firefox or Internet Explorer's rendering. Kind of hard to imagine IE actually renders something better than Chrome. I thought that would be enough to get them motivated to get this corrected. Guess I was wrong.
- kyriakos 13y agoIE11 is a really good browser. Fast and rendering is flawless