I don't think this is self-jest. Microsoft and IE team love this... the current message is "yes IE6 is broken, you should upgrade to IE8/9 because it's much better". Except that it isn't. So the funeral flowers serve them well, because they can pretend the real problem is with IE6, where in fact the problem is with them.
Microsoft has been using this "network admins don't upgrade from IE6, it's not our fault" type of argument for too long as an excuse for the mess they keep putting web standards into. If everybody suddenly upgraded to the latest and greatest IE8/9 we would still be in the same place regarding IE not following web standards. We would be free of "IE6 doesn't have a clue about the box model". But we would be at "IE8 doesn't support canvas (or proper event bubble)". Just so 9 years from now they will be sending flowers to the IE8 funeral and saying sorry for not supporting canvas... A proper solution for Microsoft now would be to completely ditch IE backend, use one of the current available libraries like Webkit, and put in place an IE frontend that can have IE6/7/8 tabs and a proper standard backend (defaulting to the proper backend). Any other move on this area coming from Microsoft seems to be either evilness or PR (which I think it's the case).
I agree with Marcelo's action on this. We're still in a very early stage of the 2.6 (stable) branch to feature freeze 2.4.
I know we need the maximum user base for 2.6 testing, debugging and to recieve those "My TV stopped working when I installed kernel 2.6" messages. But we have to take it easy.
2.6 rocks. And a lot of distros have plans to release 2.6 based releases in the first quarter of 2004, which will greatly improve the user base.
IMHO, a good feature freeze, as Marcelo said somewhere in LKML, is 2.4.24 or even 2.4.25.
It's no time for a flamewar to begin. The Beaver is in the building.:)
I don't think this is self-jest. Microsoft and IE team love this... the current message is "yes IE6 is broken, you should upgrade to IE8/9 because it's much better". Except that it isn't. So the funeral flowers serve them well, because they can pretend the real problem is with IE6, where in fact the problem is with them.
Microsoft has been using this "network admins don't upgrade from IE6, it's not our fault" type of argument for too long as an excuse for the mess they keep putting web standards into.
If everybody suddenly upgraded to the latest and greatest IE8/9 we would still be in the same place regarding IE not following web standards. We would be free of "IE6 doesn't have a clue about the box model". But we would be at "IE8 doesn't support canvas (or proper event bubble)". Just so 9 years from now they will be sending flowers to the IE8 funeral and saying sorry for not supporting canvas...
A proper solution for Microsoft now would be to completely ditch IE backend, use one of the current available libraries like Webkit, and put in place an IE frontend that can have IE6/7/8 tabs and a proper standard backend (defaulting to the proper backend). Any other move on this area coming from Microsoft seems to be either evilness or PR (which I think it's the case).
Ops, my mistake. 8)
The best movie goes for The Barbarian Invasions (France) or The Man Who Copied (Brazil).
There were lots of bad movies...but I'll give the award to one that really fought for it...Terminator 3 (USA).
I agree with Marcelo's action on this. We're still in a very early stage of the 2.6 (stable) branch to feature freeze 2.4.
:)
I know we need the maximum user base for 2.6 testing, debugging and to recieve those "My TV stopped working when I installed kernel 2.6" messages. But we have to take it easy.
2.6 rocks. And a lot of distros have plans to release 2.6 based releases in the first quarter of 2004, which will greatly improve the user base.
IMHO, a good feature freeze, as Marcelo said somewhere in LKML, is 2.4.24 or even 2.4.25.
It's no time for a flamewar to begin. The Beaver is in the building.
Those SCO guys are just playing with the Linux Community, right?
"proprietary, secure software"?
I wonder if anyone remember what was like when Caldera was a Linux distro... What happened with those guys?
"we have also announced the suspension of our own Linux-related activities"
Then what are they doing at UnitedLinux yet?
I've heard some hummors about Microsoft helping SCO at this case. Anyone knows some concrete facts about it?
I don't know what's gonna happen with this.
But, hey, here's the HL2 source code (BT link).
If this isn't a legal post, then some moderator will just remove it. Sorry.
[]s