Slashdot Mirror
Microsoft Sends Flowers To Internet Explorer 6 Funeral
Several readers have written with a fun followup to yesterday's IE6 funeral. Apparently Microsoft, in a rare moment of self-jest, took the time to send flowers, condolences, and a promise to meet at MIX. The card reads: "Thanks for the good times IE6, see you all @ MIX when we show a little piece of IE Heaven. The Internet Explorer Team @ Microsoft."
Considering the reckless life it lead, is it any surprise it finally succumbed to all those viruses?
SJW: Someone who has run out of real oppression, and has to fake it.
They should have send a blue screen of death dressed up as the grim reaper!
The Internet Explorer team has got to be the coolest group in Redmond... unless, of course, you believe the cake is a lie!
I've abandoned my search for truth; now I'm just looking for some useful delusions.
It's so sad when a parent outlives a child.
I think that's a fantastic gesture on their part. Yes, it's all in good fun, but look - one of Redmond's lawyer types could've gotten a hold of this, and gotten some judge to issue an injunction based on a combination of ip violation/unfair competition/market image tarnishing/some other frankly-my-dear-I-just-don't-give-a-damn excuse. Yeah, it'd never hold up, but nothing stopping them from just being dicks.
Instead, they took it in good fun, and did the human thing - exhibited humor. Yes, they're still evil, blah blah. But this has that WWI 1914 Christmas Eve soccer-game feel. So let's acknowledge it with good cheer.
HTML?
Peter predicted that you would "deliberately forget" creation 2000 years ago...
Sadly, Microsoft has a working fungicide but they refuse to ship it until next Tuesday.
But perhaps he's right? Everybody likes to jump on ACID as some ultimate measure of a webbrowser's worth. Neither ACID2 nor ACID3 were based on the most important or commonly used features of HTML, JavaScript and CSS, but a sampling of obscure little bits that most webbrowsers were doing wrong at the time.
As useful as ACID are, it's important to realize that they are NOT proper compliance tests. It could be argued that one of the real failings of the W3C standardization process is that they never produce a compliance test suite. So you can't accurately state that a browser (like IE) poorly supports relevant standards, without relying heavily on anecdote.