Linked by Thom Holwerda on Thu 18th Jun 2009 20:36 UTC
Internet Explorer With Internet Explorer 8 out the door, Microsoft is trying to capitalise on its latest browser release with a marketing campaign outlining several benefits Internet Explorer 8 supposedly has over Chrome and Firefox. The campaign is titled "Get the facts", so I guess most of you will know what will come.
Thread beginning with comment 369313
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: lulz
by lemur2 on Fri 19th Jun 2009 05:26 UTC in reply to "RE[6]: lulz"
lemur2
Member since:
2007-02-17

CSS 3 is an evolving standard. SVG is only referenced by HTML 5, which is an evolving standard. ECMAScript 4 is an evolving standard. And the only part where IE varies substancially from the W3C DOM standard is in its box model, and quite honestly the way they do it makes more sense then the way everyone else does it.


SVG is not an evolving standard.

http://en.wikipedia.org/wiki/Svg

Since 2001, the SVG specification has been updated to version 1.1 (current Recommendation) and 1.2 (still a Working Draft).


This does not mean that it is evolving, since SVG 1.2 is a superset that includes all of SVG 1.1.

SVG 1.1 has therefore been the standard for scalable graphics on the web for over eight years now. IE is still totally unable to deal with it.

ECMAScript 4 is abandonned.

http://en.wikipedia.org/wiki/ECMAScript

ECMAScript 3 is the current standard, and it has been the standard since December 1999, almost a decade ago.

ECMAScript 5 is not the recommended standard, and in any case it is largely a subset.

ECMAScript 5 Candidate Recommendation (Work in progress) Adds "strict mode", a subset intended to provide more thorough error checking and avoid error-prone constructs. Clarifies many ambiguities in the 3rd edition specification, and accommodates behaviour of real-world implementations that differed consistently from that specification. Adds some new features, such as getters and setters, library support for JSON, and more complete reflection on object properties. ECMAScript 5 is likely to be published as "ECMAScript 5th edition" towards the end of 2009.


No one would expect compliance with a standard that isn't out yet. Just ECMAScript 3 will do. IE has had a decade to be compliant, and doesn't manage it.

DOM Level 2 was published in late 2000. IE is compliant only with DOM level 1, which was published in 1998.

http://en.wikipedia.org/wiki/Document_Object_Model#Standardization

What would be the point in IE getting this wrong other than trying, through Windows dominance on the desktop, to make IE the only browser that would render some sites?

Now, does that matter in any way? Nope.


Oh yes it does. Ask the EU, and ask about a whopping fine that should be coming Microsoft's way.

Standards put out by consortiums tend to a) suck, and b) take forever to get out. Everyone else is a good generation ahead of what the W3C has published at this point.


Excuse me? The standards in question were all published over 5 years ago, up to 10 years ago in some cases. Everyone else is compliant, and IE alone is a generation behind.

Please try to keep up.

But when they say they support the current published standards, they are 100% correct


No, au contraire, they are 100% incorrect. They outright lie.

Edited 2009-06-19 05:33 UTC

Reply Parent Bookmark Score: 5

RE[8]: lulz
by google_ninja on Fri 19th Jun 2009 13:06 in reply to "RE[7]: lulz"
google_ninja Member since:
2006-02-05

IE is compliant with ECMAScript 3, it is things from 4 (that are now in 5) that it doesn't do so well with. For all practical reasons its compliant with DOM 2 as well. SVG has been around for ages, but html 5 is the first time it was referenced in the html spec.

The only people that care in the least about w3c web standards are web developers, and we don't care if its an evolving standard or not, we care that it is something cool that can be used reliably across all the browsers. You are trying to make this about something else, which it is not. The EU cares about bundling, they dont care about w3c compliance.

I don't really want to talk with you about this anymore, because talking with you about anything even remotely related to microsoft is an exercise in running in circles.

Reply Parent Bookmark Score: 2

RE[9]: lulz
by lemur2 on Fri 19th Jun 2009 13:21 in reply to "RE[8]: lulz"
lemur2 Member since:
2007-02-17

IE is compliant with ECMAScript 3, it is things from 4 (that are now in 5) that it doesn't do so well with. For all practical reasons its compliant with DOM 2 as well. SVG has been around for ages, but html 5 is the first time it was referenced in the html spec.

The only people that care in the least about w3c web standards are web developers, and we don't care if its an evolving standard or not, we care that it is something cool that can be used reliably across all the browsers. You are trying to make this about something else, which it is not. The EU cares about bundling, they dont care about w3c compliance.

I don't really want to talk with you about this anymore, because talking with you about anything even remotely related to microsoft is an exercise in running in circles.


You are in denial. One would feel sorry for you if you didn't keep trying to make excuses for Microsoft.

If you are finding it too hard to debate my points and you don't wish to discuss it further with me, why don't you try talking to some other web developers to see how they feel about Microsoft's noncompliance?

http://tech.slashdot.org/comments.pl?sid=1274353&cid=28387843

http://tech.slashdot.org/comments.pl?sid=1274353&cid=28388225

http://tech.slashdot.org/comments.pl?sid=1274353&cid=28388225

Here is a hint: you probably won't find a sympathetic ear there either.

Edited 2009-06-19 13:23 UTC

Reply Parent Bookmark Score: 2