Except that is not how the MS support lifecycle currently works unfortunately. It guarantees mainstream support for 5 years after this version's release, or 2 years after the next version's release, whatever is later. In other words, the only reason XP is getting more than 10 years of support is the Longhorn delays (I still remember when mainstream support for it was to end in December 31, 2006!).
Well, they are accountable to shareholders, but only to short-term stock price in most cases. I have always said no incentives is better than wrong incentives for a while now.
AFAIK with MS, mainstream support ends 5 years after that release or 2 years after the next release, whatever is later, with extended support ending 5 years after.
Yea, most computers from the Win2k and later era should be able to run WinVista/7 as long as it has enough RAM. 32-bit Vista/7 can run most XP drivers.
One of my favorite is against OS/2 in the early 1990s. The JDA was not particularly good, but the alternative MS chose ended up being much worse (look up "Microsoft Munchkins" for one example). What is worse, MS was also attacking DR-DOS, and OS/2 did not depend on DOS.
Yea, MS screwed up the protected mode transition pretty badly. Remember MS's OS/2 2.0 SDKs from 1990? The JDA was not particularly good, but the alternative MS chose was a lot worse. Remember the Chicago delays and the DR-DOS lawsuits.
BTW, this is a good time to mention that Office 2004 for Mac ended support after the January 2012 Patch Tuesday, and Office 2008 for Mac (product targeted by this exploit) ends support April 2013.
And don't forget DR-DOS. Back in 1988 when Windows was ported to protected mode by Murray Sargent, it was only beginning to be a threat, but by 1990 when 3.0 was released it was a big threat, and OS/2 did not depend on DOS at all unlike 3.x and 9x.
Yea, MS screwed up the move to protected mode so badly I could write an article about this mess. Anyone remember Multitasking DOS 4.0 which was designed for real mode despite the fact that Intel announced the 80286 in 1982?
AFAIK the exact technical problem with i915 was explaiined before as lacking a "hardware scheduler". Let me explain. Older DirectX allows only one app to use the GPU at a time. If another app tries to use the GPU, a "lost device" error would be returned to the previous app next time it does a call. This was incompatible with the DWM which uses the GPU all the time. WDDM and Direct3D9Ex allows multiple applications to use the GPU at the same time, which obviously requires hardware support.
Yea, even without this issue, running for President or Congress would be much easier if there was a +/-5% margin. I suggest running the vote again if it falls within this margin.
Slashdot Mirror
Except that is not how the MS support lifecycle currently works unfortunately. It guarantees mainstream support for 5 years after this version's release, or 2 years after the next version's release, whatever is later. In other words, the only reason XP is getting more than 10 years of support is the Longhorn delays (I still remember when mainstream support for it was to end in December 31, 2006!).
Well, they are accountable to shareholders, but only to short-term stock price in most cases. I have always said no incentives is better than wrong incentives for a while now.
dual class.
I think Ellison is the co-founder of the company.
AFAIK with MS, mainstream support ends 5 years after that release or 2 years after the next release, whatever is later, with extended support ending 5 years after.
In fact, with Microsoft, Custom Support for Windows is generally $200,000 for first year and more afterwards.
Yea, most computers from the Win2k and later era should be able to run WinVista/7 as long as it has enough RAM. 32-bit Vista/7 can run most XP drivers.
One of my favorite is against OS/2 in the early 1990s. The JDA was not particularly good, but the alternative MS chose ended up being much worse (look up "Microsoft Munchkins" for one example). What is worse, MS was also attacking DR-DOS, and OS/2 did not depend on DOS.
And SCSI is a standard interface. You can replace the controller card and still use your old SCSI scanners with it.
Note that you can install 32-bit Win7 to use your old XP drivers.
Wonder how many enterprises will end up buying the expensive Custom Support Agreements.
XP will end support in exactly two years (April 2014).
Fortunately, HTML now includes the bdi tag, which is implemented in recent browsers such as Firefox 10, to solve this problem.
Yes it is possible, in fact:
http://www.cultofmac.com/154873/tim-cook-forces-att-to-unlock-customers-phone/
Notice the phone involved.
See this story:
http://www.cultofmac.com/154873/tim-cook-forces-att-to-unlock-customers-phone/
utter assholes like Vic Gundotra (the asshole behind the Real Names fiasco)
Ah, I even did a Slashdot submission on this one:
http://slashdot.org/submission/1778830/google-is-gagging-user-advocates
As I mentioned in this post, I consider the employee gagging the worst part of the fiasco.
Lots about this stuff in MS anti-trust exhibits, BTW:
http://news.ycombinator.com/item?id=3441885
Yea, MS screwed up the protected mode transition pretty badly. Remember MS's OS/2 2.0 SDKs from 1990? The JDA was not particularly good, but the alternative MS chose was a lot worse. Remember the Chicago delays and the DR-DOS lawsuits.
BTW, this is a good time to mention that Office 2004 for Mac ended support after the January 2012 Patch Tuesday, and Office 2008 for Mac (product targeted by this exploit) ends support April 2013.
Yea, this particular vulnerability has nothing to do with macros.
I remember Microsoft just about killed themselves getting Windows 95 done, in reaction to OS/2's stronger than expected showing.
BTW, the MS anti-trust exhibits contains a lot of emails about this fiasco. Here is an interesting one:
http://www.groklaw.net/pdf/iowa/www.iowaconsumercase.org/011607/0000/PX00307.pdf
And don't forget DR-DOS. Back in 1988 when Windows was ported to protected mode by Murray Sargent, it was only beginning to be a threat, but by 1990 when 3.0 was released it was a big threat, and OS/2 did not depend on DOS at all unlike 3.x and 9x.
Yea, MS screwed up the move to protected mode so badly I could write an article about this mess. Anyone remember Multitasking DOS 4.0 which was designed for real mode despite the fact that Intel announced the 80286 in 1982?
AFAIK the exact technical problem with i915 was explaiined before as lacking a "hardware scheduler". Let me explain. Older DirectX allows only one app to use the GPU at a time. If another app tries to use the GPU, a "lost device" error would be returned to the previous app next time it does a call. This was incompatible with the DWM which uses the GPU all the time. WDDM and Direct3D9Ex allows multiple applications to use the GPU at the same time, which obviously requires hardware support.
Yea, even without this issue, running for President or Congress would be much easier if there was a +/-5% margin. I suggest running the vote again if it falls within this margin.