Chrome font rendering killed itself today. And you?

File: Screen Shot 2016-06-10 at 15.04.24.png (242KB, 1239x1165px) Image search: [Google]

242KB, 1239x1165px

>>55008349
works on my machine pham, maybe your OS is the problem

>>55008371
Could well be, I'm on 51.0.2704.84 m by the way.

W10, so font rendering was never very good in the first place.

File: Screen Shot 2016-06-10 at 15.09.38.png (30KB, 433x307px) Image search: [Google]

30KB, 433x307px

>>55008400
I'm on canary actually

>>55008425
Guess I should step it up.

>>55008349
Sounds like a windows problem. Why doesn't Windows have good font rendering anyway? Is it because they render fonts in the kernel?

>>55008490
goy, you are supposed to have a 300 dpi screen for windows devices

>>55008490
Fuck if I know, but canary fixed it, guess it was just a shitty version.

Fonts are pretty good on W10 though desu.

>>55008508
The kerning though, how is 300dpi going to compensate for that?

>>55008519
I'm just messing with you, 120 dpi would be enough.

the pixels would be so small, you wouldnt notice the bad font rendering

why does windows have a shitty font rendering compared to OSX?

i remember there was a program years ago that emulated the osx font rendering, but even when i found it years ago, it was an abandoned piece of software for many more years before i found it

>>55008561
mactype???

>>55008561
Mactype still works flawlessly on windows. Still it's too bad chromium project remove flag to disable directwrite after version 52.

>>55008648
>Mactype still works flawlessly on windows

Really? Last I checked, Mactype looked weird on some programs.

>>55008742
It does. It's far from flawless and it also has kerning issues.

>>55008648
mactype make windows 10 (insider build) exporer.exe crashes like crazy.

Stupid question here:

What makes font rendering so difficult?