Knowing that people using Windows 2000 are stuck with IE6 - despite the fact that their machine still suits their needs - is why we need to continue to push people away from IE. Even if IE9 is amazing.
Firefox 3.6 STILL works on Windows 2000 (http://www.mozilla.com/en-US/firefox/system-requirements.htm...). Until Microsoft releases a browser we know isn't going to put us in the "I can't upgrade past IE6" situations that we hear about, I'll proudly support everything that isn't Internet Explorer.
(Note: Has anyone ever tried to submit a bug report to Microsoft? It is impossible! I even put together http://crashie8.com/ as a proof of concept, and I still can't get anyone to acknowledge the problem!)
Even Firefox is getting their act together and their next release is very much inspired by chrome.
Also, marketshare is not necessarily the primary motivator for every developer. A lot of the Firefox developers are motivated to put the best browser possible out there, regardless of marketshare, the fact that there is a leaner, meaner, faster browser even exists (even if the marketshare was less than 1%) might be enough motivation for them to innovate.
Partly - I think we are jaded because of technical flaws as well, even in their later versions. IE8 was supposed to be their modern browser, and it still had no canvas support and horrible JS performance.
Otherwise, I agree with you - even if IE9 is a huge hit and awesome, a lot of developers supporting IE won't really have a better life.
More so, there doesn't appear to be any significant sense of urgency in the IE team related to just how far behind they are. Firefox has revolutionized its Javascript engine, massively increased standards compliance, and added support for next generation html5 and css3 features. We'll be lucky if IE9 manages to support css 2.1 correctly, let alone implements html5, css3, or comes out with a competitive javascript engine.
Microsoft seems to be pretty complacent in regards to IE because it still dominates marketshare. However, the decline of Myspace shows just how quickly marketshare in the online world can change.
Why would or should they go back to developing a free browser for an out of support system which will mess up the user's system as a deliberate side effect, for the benefit of some arbitrary web developers?
To put it another way—if there was an update they could release to Windows 2000, at this point, that people would install voluntarily, but would make more people buy Windows 7 as an effect, don't you think Microsoft would be all over that?
I couldn't give a damn about supporting unfinalised
standards the ACID3 tests
MS too sometimes speaks of Acid3 in dismissive terms as having little relevancy. Let's see and then decide by yourself, is this stuff important: DOM2 Core
DOM2 Events
DOM2 HTML
DOM2 Range
DOM2 Style (getComputedStyle, …)
DOM2 Traversal (NodeIterator, TreeWalker)
DOM2 Views (defaultView)
ECMAScript
HTML4 (<object>, <iframe>, …)
HTTP (Content-Type, 404, …)
Media Queries
Selectors (:lang, :nth-child(), combinators, dynamic
changes, …)
XHTML 1.0
CSS2 (@font-face)
CSS2.1 (‘inline-block’, ‘pre-wrap’, parsing…)
CSS3 Color (rgba(), hsla(), …)
CSS3 UI (‘cursor’)
data: URIs
SVG (SVG Animation, SVG Fonts, …)
(Taken from: http://www.webstandards.org/action/acid3/)Looks important to me.
And as mentioned, one of them is a speed test which is affected by external circumstances.
I'm not saying its irrelevent, but I am saying that a 100% pass rate doesn't mean its 100% compliant with the things being tested. Furthermore, we shouldn't be punishing companies which aren't willing to implement support for standards which are drafts.
ACID2 was genuinely useful because it was all finalised standards. ACID3 though I think could have done better.. So its nice to pass, but a 100% pass just says you are compliant with 100 tests. I'm betting the compliance testing suites used by browsers are a LOT more comprehensive..
CSS3 isn't a finalised standard, and the test only tests a
few things. You do realise there is a lot which this
doesn't test too right?
That's exactly my point: Acid3 test the important bits, the parts of the spec which are useful. This test is web apps oriented (hence a strong focus on DOM manipulation and dynamic behavior) and thats where web is heading now. I couldn't give a damn about supporting unfinalised standards the ACID3 tests
...
HTML4
Saying HTML4 is important in reply to a comment about unfinalized standards is a bit of a non sequitar, no?Personally, no, I don't give a damn about SVG, but I'd be pretty upset if my browser didn't support iframes. Does the Acid3 test weight its tests appropriately?
In fact, its interesting that their new engine is so fast. Its going to get very interesting, especially since personally, I couldn't give a damn about supporting unfinalised standards the ACID3 tests (in fact, one of the ACID3 tests can't be passed 100% of the time anyway).
Speed is important, and since a lot of applications use the IE engine, maybe this will speed up some other applications as well.
Btw, I can confirm their sunspider benchmark.. Their preview does run faster than Firefox on my system (although, unsure if my addons are having an impact on that, or external causes). As its just a preview, it should only be taken with a grain of salt anyway..