Yea, in fact IE6 was the first version of IE where MS focused on standard compliance instead of adding new features, partly thanks to complaints from the WaSP and also thanks to DOCTYPE switching.
(which is a fair criticism - Vista came out long after OS X, which had similar compositing going on, which worked on old 4Mb ATI Rage 3D chipsets - I'm not kidding, Jaguar worked perfectly on an old Beige G3 that had that chipset)
Part of the problem I think is that the old XPDM based DirectX did not allow more than one app to access the GPU at a time (the old app would receive a device lost error next time it tries to access the graphics card). And for the record, the reason why i915 never had a WDDM driver is probably because allowing more than one app to access the GPU at a time required hardware support (which is probably what the "hardware scheduler" did). Notice it only supports up to OpenGL *1.4*.
(just how many OEM Dr. DOS or OS/2 installs did you ever see on PC compatibles).
Ah, OS/2 and DR-DOS. Remember the MS OS/2 2.0 SDKs back in 1990? Yes, the JDA was not particularly good, but the anti-competitive tactics used to attack OS/2 later on was even worse. And on DR-DOS, OS/2 never depended on DOS, and by the time Win3.0 was released, DR-DOS 5.0 was already released too. The Chicago project was delayed while MS was attacking OS/2 in the meantime, delaying the popularity of 32-bit programming by years! By the time MS finally released Win95, the 386 itself was almost obsolete, while IBM was able to release OS/2 2.0 in 1992! And on DR-DOS, the Win95 dependence on DOS for booting helped Caldera drag the lawsuit DR started against MS by another few years! Yea, I could write an entire article on this mess.
AFAIK Stuxnet was developed before Win2000 ended support and was discovered just after, which means it did target Win2K, but patches for the vulns Stuxnet targeted are not available for Win2k without a CSA. This is a targeted attack though.
Slashdot Mirror
BTW Server 2003 ends support on July 14, 2015, slightly more than a year after XP:
http://support.microsoft.com/lifecycle/search/default.aspx?alpha=Windows+Server+2003
Yea, in fact IE6 was the first version of IE where MS focused on standard compliance instead of adding new features, partly thanks to complaints from the WaSP and also thanks to DOCTYPE switching.
Yea, MS already has the expensive Custom Support Agreements, and already have Shared Source too that could be extended for this purpose.
Not till the end of 2014, till *April* 2014.
In particular, XHTML and DOM Level 2 are 10 years old! Though to support DOM Level 2 in IE9 required major changes to the DOM.
Yea, IE7 changed very little about the DOM but IE8 did change the DOM to be a bit more Level 1 compliant.
The difference is that back in the days when Amiga was dying, the PC was considered far from dead.
Win7 and even Win8 still support BIOS booting and should boot in legacy mode.
Yea, that tells a lot about what it was originally designed for.
Not to mention that you will still be able to access the Windows desktop and install your own software on x86-based computers and tablets.
I know:
http://www.mozillazine.org/talkback.html?article=1708
(which is a fair criticism - Vista came out long after OS X, which had similar compositing going on, which worked on old 4Mb ATI Rage 3D chipsets - I'm not kidding, Jaguar worked perfectly on an old Beige G3 that had that chipset)
Part of the problem I think is that the old XPDM based DirectX did not allow more than one app to access the GPU at a time (the old app would receive a device lost error next time it tries to access the graphics card). And for the record, the reason why i915 never had a WDDM driver is probably because allowing more than one app to access the GPU at a time required hardware support (which is probably what the "hardware scheduler" did). Notice it only supports up to OpenGL *1.4*.
Funny that Intel once made the XScale ARM rpocessor.
They did not have to throw away P4 because of RDRAM, but they did have to throw away Timna.
AFAIK the Adobe CEO holds both a CS and a MBA degree:
http://en.wikipedia.org/wiki/Shantanu_Narayen
"Mailing batteries internationally, or to and from APO, FPO, or DPO destinations is prohibited regardless of mail class."
(just how many OEM Dr. DOS or OS/2 installs did you ever see on PC compatibles).
Ah, OS/2 and DR-DOS. Remember the MS OS/2 2.0 SDKs back in 1990? Yes, the JDA was not particularly good, but the anti-competitive tactics used to attack OS/2 later on was even worse. And on DR-DOS, OS/2 never depended on DOS, and by the time Win3.0 was released, DR-DOS 5.0 was already released too. The Chicago project was delayed while MS was attacking OS/2 in the meantime, delaying the popularity of 32-bit programming by years! By the time MS finally released Win95, the 386 itself was almost obsolete, while IBM was able to release OS/2 2.0 in 1992! And on DR-DOS, the Win95 dependence on DOS for booting helped Caldera drag the lawsuit DR started against MS by another few years! Yea, I could write an entire article on this mess.
With their iOS devices, yes. The Macs are just as open as before though.
Except that back in that era the FSF/GNU project was not well known.
At least some of the bugs above are fixed in IE10 which will come with Windows 8/RT.
At least until the end of life of Windows XP, the role of holding everybody back falls to IE8. HTML5? No show.
Or even the 10 years old XHTML and DOM2!
Last time I checked, 6 months after publication it becomes open access and public via GetIEEE802.
Reminde me of this: http://www.reddit.com/r/programming/comments/lchhd/ban_programmers_not_functions_about_memcpy_s/
True, but there are targeted attacks even in the Unix world, and if you don't keep it up-to-date, you could be owned by one of them
AFAIK Stuxnet was developed before Win2000 ended support and was discovered just after, which means it did target Win2K, but patches for the vulns Stuxnet targeted are not available for Win2k without a CSA. This is a targeted attack though.