Crisp Graphical Rendering Slated for Chrome 37

Chrome has historically used the Windows Graphics Device Interface (GDI) to power text rendering on their Windows browser, a technology that has been around since the original release of Windows in the mid 80s. Chrome 37 for Windows will now adopt DirectWrite, a text layout and glyph rendering Windows API introduced with the release of Windows 7 in 2009. DirectWrite is said to improve browsing performance with “high-quality text rendering even on high-DPI displays.” 

This move by Chrome is a culmination of user requests, forum discussion, and sandboxing since the DirectWrite API’s debut. It also follows the adoption of DirectWrite by FireFox and IE9 in 2011. It took longer for Chrome, given the re-architecting and streamlining needed to implement the API. Currently, Chrome 36 uses GDI, but if all goes to plan, version 37 is scheduled to dump GDI and embrace DirectWrite within the next stable release.

Original Article

Chrome gets sharp after dumping 30-year-old Windows technology

Bill Doerrfeld I am a consultant that specializes in API economy research & content creation for developer-centric programs. I study Application Programming Interfaces (APIs) and related tech and develop content [eBooks, blogs, whitepapers, graphic design] paired with high-impact publishing strategies. I live and work in Seattle, and spend most of my time as Editor in Chief for Nordic APIs, a blog and knowledge center for API providers. For a time I was a Directory Manager & Associate Editor at ProgrammableWeb, and still add new APIs to the directory every now and then. Drop me a line at bill@doerrfeld.io. Let's connect on Twitter at @DoerrfeldBill, or follow me on LinkedIn.

Comments