This is slightly incorrect as the problem only affects Google Chrome on Windows. Also, the Chrome team is actively working on this problem as seen in in its issue report [1]. The progress can be seen by launching Chrome Canary with the --enable-direct-write flag. chromestatus.com indicates that its scheduled to be released in M36.
Chrome for Windows is one of the most common setups for browsing the internet, so this isn't an edge case situation. That post originated in 2009, over 4.5 years ago.
It's good to hear it might be finally addressed, but I wouldn't say they've been actively working on it, when all the other popular browsers had this sorted years ago.
[1] https://code.google.com/p/chromium/issues/detail?id=25541