IE upgrade cuts off QuickTime

by Bill Pena

Related link:

I can't even count the number of things broken on my Windows machines by installing Windows Media Player or previous IE Service Packs, including disabled DVD drives, crashing loops, and all-out reinstalls of the OS. Now, anyone who uses Windows Update in any normal fashion (or, with Windows ME, is repeatedly pounded over the head to update their system) will lose the ability to use Quicktime and other plugins in IE. Infuriating.

There are two disconcerting effects of this move: first, Microsoft has already decided to leave out Java from Windows XP, so ActiveX will be the only glue for desktop-to-web connectivity, web apps, and other client-side applications where plugins or Java are usually deployed.

Secondly, ActiveX is a notorious security hazard. Like no other browser component, MS has had to release security patch after security patch to plug the holes in ActiveX. Considering the recent damages created by the Code Red virii, which exploited Microsoft's IIS, and the recent discovery of another security hole in Hotmail, Microsoft's reputation for security is atrocious.

Sadly, the process by which security problems are fixed -- Service Packs and Windows Update -- is the same process MS has just used to disable compatability with competing technology, and require the use of a less secure alternative. How does this bode for a .Net future, where MS controls the flow of entire applications, databases of personal information, and the authentication mechanism -- Passport -- to access them?


2001-08-21 21:36:20
Browser wars
Microsoft had won the browser wars. Now it is time for Microsoft to pluck its fruits.

During the battle it lost a few court cases and it uses this as an excuse to change things around. There are however two things to note.
1 This is the behaviour of a monopolist hence the consequences for the rest of the market. Microsoft could have settled with Sun by providing full and standard Java. Microsoft could have settled and payed up for infringing on other peoples patents.
2 This is NOT beneficial to people to businesses. It is a step back in functionality.

A lot of people and BUSINESSES will reconsider their browser functionality. When they see sharp again it will move them away from the whole dotnet.

Funny that Mozilla is almost at their version one. Maybe Microsoft wanted to start the browser war now fearing a full version ??