Live data from Hacker News

An Early Look At IE9 for Developers

blogs.msdn.com

11–20 of 96 posts

Re: An Early Look At IE9 for Developers

#11
> "perceiving the differences may be difficult on real-world sites"

Geee, I wonder why?

Could it be because noone can use javascript properly on real world sites because IE6, IE7, IE8 have effing 1/100th the javascript performance as any other major browser????

Re: An Early Look At IE9 for Developers

#12
Regarding hardware-accelerated drawing of text:

I thought that IE just like any other Windows program is using Windows core APIs like GDI+ to display text. And those APIs, in turn, are hardware-accelerated as much as possible. These days the entire desktop is essentially a "game" running on top of DirectX, no?

Even back in 1995 most of GDI 2D functions were hardware-accelerated, assuming you had a good card with good drivers.

What am I missing? (I haven't done any Windows work in 5 years).

Re: An Early Look At IE9 for Developers

#15
post #5
post #3

Earlier quoted context omitted.

At least it's almost as fast as the slowest competitor...

Yeah, I love how they say IE is no longer an "outlier." They need to use trickery in the graph so that it's hard to tell that it's still 3x slower than Chrome or Safari.

They did show how IE8 is orders of magnitude slower than its competitors - that display of honesty shocked me a little.

Re: An Early Look At IE9 for Developers

#16
post #13

Summary: still a long way to go. No announcement yet on @font-face, canvas, video. Basic performance improvements.

The @font-face spec doesn't mention a font standard, and Microsoft have already said they won't implement TTF or OTF because the font foundries don't like it.

It's possible that IE will implement the upcoming WOFF (Web Open Font Format) standard in IE9 but I wouldn't rely on it.

Re: An Early Look At IE9 for Developers

#17

Regarding hardware-accelerated drawing of text: I thought that IE just like any other Windows program is using Windows core APIs like GDI+ to display text. And those APIs, in turn, are hardware-accelerated as much as possible. These days the entire desktop is essentially a "game" running on top of DirectX, no? Even back in 1995 most of GDI 2D functions were hardware-accelerated, assuming you had a good card with good…

The part of the post about the font rendering is BS anyway. The picture is supposed to show "sub-pixel positioning" and it only shows antialiasing (not even sub-pixel antialiasing) which as you've pointed out isn't handled by a browser anyway.

"Sub-pixel positioning" on the other hand would indeed need to be handled inside of the browser, so that the engine knows how much space something takes up so it can position the next item- But the picture accompanying the post is wrong/irrelevant.

Post reply on HN