This means that I have to edit any page that I use QT on. Thats about 100-120 pages. Grrr. 5-6 hours of work right down the tubes. All because Microsoft is being a typical prick.
Microsoft Internet Explorer for Windows, versions 5.5 SP2 and 6.0 (soon to be released) no longer support Netscape-style plug-ins (Emphasis added)
mean that other plug-ins besides QT are also affected, so that anybody whose web pages require them will have to make changes? Is MS effectively breaking a significant number of web pages out there by changing the way MSIE uses plug-ins?
I think this may have been to prevent people 'fixing' their Macs.
You tell a predominantly Mac audience (Quicktime Developers) that there is a problem with IE, you better darned well make it clear that this is Windows only. I bet they still get calls on how to install the ActiveX on somebodies G4 (sad but true, people are idiots).
The amazing thing is that Microsoft has no clue how angry this is going to make a significant portion of the web authors. They actually believe that Windows media player is better (sure, I want to put up with huge numbers of dropped frames even on a fast connection, sure I do) and want to shove it down peoples throats. And they wonder why a significant amount of the computing profession supports anti-trust action against them.
Microsoft Internet Explorer for Windows, versions 5.5 SP2 and
6.0 (soon to be released) no longer support Netscape-style
plug-ins (Emphasis added) mean that other plug-ins besides QT
are also affected, so that anybody whose web pages require them
will have to make changes? Is MS effectively breaking a
significant number of web pages out there by changing the way
MSIE uses plug-ins?
I thought that would happen too, but I haven't seen any reports anywhere of this. When you install, say, Flash on Windows, does it install a different plug-in dependning on whether it's going into IE or NS? Or can one plug have code to handle both NS and AX plugins and Apple just didn't have any AX code in them?
Anyway, this is the beginning of the end of the 'open' web in my book... embrace & extend... yeah...
Re: I think this may have been to prevent people 'fixing' their Macs.
The amazing thing is that Microsoft has no clue how angry this
is going to make a significant portion of the web authors. They
actually believe that Windows media player is better (sure, I
want to put up with huge numbers of dropped frames even on a
fast connection, sure I do) and want to shove it down peoples
throats. And they wonder why a significant amount of the
computing profession supports anti-trust action against them.
Amen to that.
I have yet to experience a Microsoft media technology which was superior in any way to a contemporary technology developed by anyone else.
They're being right bastards with this. They got their share, They got enough wiggle room from their DOJ lawsuit, now it's time to hang consumers out to dry.
Re: I think this may have been to prevent people 'fixing' their Macs.
Hmm well I can't call it superior, but real certainly isn't any
better than Media player (c=
Quality-wise, my experience with Real has always been better than with Media Player. Maybe that's just cos of what I was watching (no, not digitized circa-50's-era stag films).
Comments
http://www.apple.com/quicktime/products/tutorials/activex.html
This means that I have to edit any page that I use QT on. Thats about 100-120 pages. Grrr. 5-6 hours of work right down the tubes. All because Microsoft is being a typical prick.
- Infininight, the vengeful
[img]http://www.mythvillage.org/~msheets/namebanner.gif[/img]
I had to giggle just a bit when I saw their note (in red italic text):
Note: This issue affects only users of Internet Explorer on Windows.
In other words...
Note: This issue affects only 80% of web browsers in use today.
_/ C
(yes, you read that right--and that's being generous)
...does this: mean that other plug-ins besides QT are also affected, so that anybody whose web pages require them will have to make changes? Is MS effectively breaking a significant number of web pages out there by changing the way MSIE uses plug-ins?
You tell a predominantly Mac audience (Quicktime Developers) that there is a problem with IE, you better darned well make it clear that this is Windows only. I bet they still get calls on how to install the ActiveX on somebodies G4 (sad but true, people are idiots).
The amazing thing is that Microsoft has no clue how angry this is going to make a significant portion of the web authors. They actually believe that Windows media player is better (sure, I want to put up with huge numbers of dropped frames even on a fast connection, sure I do) and want to shove it down peoples throats. And they wonder why a significant amount of the computing profession supports anti-trust action against them.
I thought that would happen too, but I haven't seen any reports anywhere of this. When you install, say, Flash on Windows, does it install a different plug-in dependning on whether it's going into IE or NS? Or can one plug have code to handle both NS and AX plugins and Apple just didn't have any AX code in them?
Anyway, this is the beginning of the end of the 'open' web in my book... embrace & extend... yeah...
Amen to that.
I have yet to experience a Microsoft media technology which was superior in any way to a contemporary technology developed by anyone else.
They're being right bastards with this. They got their share, They got enough wiggle room from their DOJ lawsuit, now it's time to hang consumers out to dry.
Sigh.
...ken
Hmm well I can't call it superior, but real certainly isn't any better than Media player (c=
-Cunbelin
Quality-wise, my experience with Real has always been better than with Media Player. Maybe that's just cos of what I was watching (no, not digitized circa-50's-era stag films).
_/ C