Linked by Kroc Camen on Sat 26th Jun 2010 10:48 UTC
Permalink for comment 431608
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



Member since:
2007-02-17
Direct2D is Windows-only. If one writes an application to use Direct2D, then it is forever doomed to be a Windows-only application.
All of IE9's competition (that is, other competitive browsers, to whit: Opera, Firefox, Chrome and Safari) are all cross-platform applications. They all use APIs that are not going to doom them into being Windows-only applications.
OpenGL on Windows is crippleware. OpenGL or Xrender would be the APIs that other browsers would use, and not Direct2D. Firefox uses Cairo, for example, and hardware acceleration for Cairo is being done via OpenGL. This will work well everywhere except Windows.
https://wiki.mozilla.org/Platform/GFX/HardwareAcceleration
Follow-on work for this might include making a Direct3D/Direct2D backend, especially if it's found that OpenGL stability/availability on Windows isn't sufficient.
So applications like Firefox for Windows have to write functionality like hardware acceleration twice. They have to write it once for most platforms using Xrender or OpenGL, and then they have to write it again for Direct2D, just for Windows:
http://www.basschouten.com/blog1.php/2010/03/02/presenting-direct2d...
It will happen, but it will take a bit longer. This is just another way for Microsoft to make other teams look slower, for Microsoft to write its applications to be Windows-only, and in general to create a software corpus which is harder to make cross-platform than it needs to be if Microsoft had stuck with standard APIs.
Edited 2010-06-26 15:09 UTC