Linked by Thom Holwerda on Wed 6th Jan 2010 20:01 UTC
Internet Explorer It would appear that Microsoft will finally take standards compliance in the browser world seriously, after dragging its feet for years. Back in November 2009, the Redmond giant already revealed that Internet Explorer 9 would come with CSS3 and HTML5 support, and now the cup runneth over, as Microsoft has requested to join the W3C's SVG Working Group.
Thread beginning with comment 402904
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by Kroc
by Kroc on Wed 6th Jan 2010 22:08 UTC in reply to "RE[3]: Comment by Kroc"
Kroc
Member since:
2005-11-10

Yes it loses to other browsers in JS benchmarks

By 100–1000×. IE8 is mind-blowingly slow.

Real-world differences are minimal.

Like taking almost 10 seconds to open a new—blank—tab.

As for HTML5 the default video codec still hasn't been decided

There is no default video codec. That’s like saying there’s a default image format—there isn’t one.

FF OSX which annoyingly cannot be counted on to render websites identically to FF Windows.

Which is what it is supposed to do.

Reply Parent Score: 1

RE[5]: Comment by Kroc
by nt_jerkface on Wed 6th Jan 2010 22:51 in reply to "RE[4]: Comment by Kroc"
nt_jerkface Member since:
2009-08-26


By 100–1000×. IE8 is mind-blowingly slow.

Where is it mind-blowingly slow? I just created new google docs in both Chrome and IE8, and the latter took about 3 seconds more at the most.


Like taking almost 10 seconds to open a new—blank—tab.

Takes 1 second on my machine. Are you using a P3?


There is no default video codec. That’s like saying there’s a default image format—there isn’t one.

There isn't a default codec because there is currently a debate over which one it should use:
http://arstechnica.com/open-source/news/2009/07/decoding-the-html-5...


Which is what it is supposed to do.


No I don't think you understand. When you develop a complex AJAX website you can't expect FF OSX and FF Win to render it in the same manner. I'm not just talking about different looking buttons but enough quirks between the two codebases to treat them as separate browsers. Kind of makes a joke of FF following web standards when you have to keep an instance of OSX to test in.
Interestingly I didn't have any problems with the webkit browsers.

Reply Parent Score: 2

RE[6]: Comment by Kroc
by Kroc on Wed 6th Jan 2010 23:24 in reply to "RE[5]: Comment by Kroc"
Kroc Member since:
2005-11-10

I use IE8 on brand new OEM machines I’m setting up for people and 10 seconds to open a tab is not out of the ordinary. It might take you 1 second, but the majority of users don’t get anything like that. The fact is that any other browser is simply faster than IE8 in every department.

As for FF OS X? The trick is to write in FF OS X and fix for Windows, not the other way around. FF/Mac’s rendering is much more accurate (even supporting better ligatures than Webkit).

Reply Parent Score: 1

RE[6]: Comment by Kroc
by abraxas on Thu 7th Jan 2010 03:17 in reply to "RE[5]: Comment by Kroc"
abraxas Member since:
2005-07-07

IE8 has decent JS, Google docs works in it just fine. Yes it loses to other browsers in JS benchmarks but that doesn't mean that AJAX developers are held back by IE. Those benchmarks are mostly used by Google for bragging rights. Real-world differences are minimal. Your browser is more likely to choke on a small Flash ad than a website filled with JS.


Perhaps you haven't used another browser then. JS on IE is orders of magnitude slower than JS on Gecko or Webkit based browsers.

Reply Parent Score: 2

RE[5]: Comment by Kroc
by PlatformAgnostic on Wed 6th Jan 2010 23:27 in reply to "RE[4]: Comment by Kroc"
PlatformAgnostic Member since:
2006-01-02

On the topic of 10-second tab open times, that's mostly a function of what plugins are loaded (each tab is a new browser instance, so plugins need to be reinitialized).

Go to "Tools->Manage Addons..." and look at the 'load time' column of the addons list to see what's taking all the time.

Reply Parent Score: 2

RE[6]: Comment by Kroc
by Kroc on Thu 7th Jan 2010 07:41 in reply to "RE[5]: Comment by Kroc"
Kroc Member since:
2005-11-10

Yes, of course, but I’m saying what the end user sees and they don’t know how to manage the BHOs. I go to a user’s PC and IE is crawling. I install Firefox, and bingo, everything is instantly faster and the user is overjoyed.

Perception people, perception. What the average end-user experiences of IE8—regardless of outside interference from other apps and add-ons (because they don’t know about that)—is a pain-inducingly slow browsing experience.

Reply Parent Score: 1

RE[6]: Comment by Kroc
by oskar.h on Thu 7th Jan 2010 14:54 in reply to "RE[5]: Comment by Kroc"
oskar.h Member since:
2008-07-29

That actually made a difference. I disabled all addons (Messenger, Research, Java etc.) and now my IE8 isn't so much slower than FF.

I get the feeling that a lot of those addons could be loaded when I need them instead of each time a new tab is created. Take Java for example (which took ~1s to load). I would be just fine with waiting that extra second when I actually need Java...

Reply Parent Score: 1