Chrome Beta download: You are about to participate in a great adventure.
Google (NASDAQ:GOOG) brings beta browser, with DirectWrite support. Beta 37 should quell complaints that Windows font rendering is slow and blurry.
The ancient Graphics Device Interface (GDI) calls have finally been replaced -- by using the outer limits of DirectWrite.
In IT Blogwatch, bloggers initially eulogize: GDI API RIP.
Your humble blogwatcher curated these bloggy bits for your entertainment.
Frederic Lardinois likes bacon:
Google released the latest beta version of its Chrome browser [for] Windows [and] fonts will now look better...because [it] now supports Microsoft’s DirectWrite API.
…Users have long asked Google to make this switch, but the company says that it "required extensive re-architecting and streamlining." [It] also now supports subpixel font scaling, which enables smooth animations of text between font sizes, and better support for touch events. MORE
And Seth Rosenblatt sharpens up the reporting:
It's taken four and a half years but the engineering gurus...have finally improved how the browser renders text on Windows. [It] previously rendered text with [GDI] which dates back to the mid-1980s. The bug to get Chrome to support DirectWrite was filed in October 2009
…Chrome 37 Beta...is due to graduate to the most-heavily used Stable channel in around six weeks. MORE
So Google's Emil A. Eklund directly writes:
Graphics Device Interface (GDI)...reflects the engineering tradeoffs of that time, particularly for slower, lower-resolution machines.
…[Windows] users should begin seeing better-looking fonts and increased rendering performance as we roll out DirectWrite, with no changes required by web developers. MORE
But Aaron Boodman sees the irony: [You're fired -Ed.]
The image in the blog post got stretched, so that both [examples] look like poo. If you click on the image, you can see the point that the post was actually trying to make. MORE
Meanwhile, Emil Protalinski notes another ancient Microsoft standard that Chrome deprecated:
Chrome 37 will disable support for showModalDialog by default. First introducted in Internet Explorer 4, the API allows applications to show a dialog...that freezes all other content. Google says it has found less than 0.006 percent of pages use it.
…Since many enterprise sites rely heavily on showModalDialog, Google has added a temporary Enterprise Policy setting to re-enable it. In May 2015, this setting will be removed and showModalDialog will be completely killed off. MORE
Subscribe now to the Blogs Newsletter for a daily summary of the most recent and relevant blog posts at Computerworld.