Linked by Kroc Camen on Sat 26th Jun 2010 10:48 UTC
Internet Explorer Microsoft have released IE9 Platform Preview 3, an application that gives developers access to the IE9 rendering engine (it's not a full browser). In this update they have added hardware accelerated HTML5 Video, Canvas, Fonts (using WOFF) and big improvements in JavaScript with ES5, DOM Traversal, L2 and L3 events and 83/100 Acid3 score. It sits between Firefox and Chrome 6 on JavaScript speed, but outperforms every browser in real tests.
Thread beginning with comment 431599
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Real tests
by sukru on Sat 26th Jun 2010 14:12 UTC in reply to "RE[4]: Real tests"
sukru
Member since:
2006-11-19

Yes, that's called Aero and Windows Presentation Framework.

Seriously, even after all these anti-trust sanctions, people still think MS is using hidden APIs for non-core OS functionality. The APIs are openly documented, they - legally - cannot use hidden ones.

Reply Parent Score: 10

v RE[6]: Real tests
by lemur2 on Sat 26th Jun 2010 14:34 in reply to "RE[5]: Real tests"
RE[7]: Real tests
by Nelson on Sat 26th Jun 2010 16:38 in reply to "RE[6]: Real tests"
Nelson Member since:
2005-11-29

Why doesn't Microsoft just write the browser for them? Seriously? A system-wide canvas library? What on earth?

Microsoft does the best that they could, Direct2D is a relatively simple API (though still a COM API, but ugh), but simple nonetheless.

HW Accelerated canvas drawing is simply a consequence of the entire renderer being written in Direct2D.

Reply Parent Score: 3

RE[7]: Real tests
by Moochman on Sat 26th Jun 2010 16:55 in reply to "RE[6]: Real tests"
Moochman Member since:
2005-07-06

The problem is that Windows APIs are unique to Windows, and they don't use a common API (such as something similar to Canvas) that could accelerate all applications.

Therefore, each cross-platform application on Windows is required to write its own hardware-acceleration for rendering built in to the application, rather than it being available as a system-wide library to call.


There is a system-wide library to call, it's just not the same one that's available on Mac or on Linux, each of which have their own (multiple, in fact) system-wide libraries to call.

It's really unclear what you are asking for that isn't already present in Windows, and what you think Windows lacks that is somehow magically present elsewhere. Cross-platform apps that use normal widgets can use cross-platform toolkits like Qt... which already offers native hardware acceleration on a number of platforms. Or they can just use OpenGL directly.....

The reason Firefox and apps written in other toolkits don't already support hardware-accelerated rendering is as I understand it because they use low-level, CPU-based (not GPU-based) calls to figure out how to render stuff. There's really not a whole lot that can be done without some sort of rewrite.

Edited 2010-06-26 17:09 UTC

Reply Parent Score: 4