Adopting as I can
04-13-2000, 11:18 AM
For myself, I hate stuff not working on my browser; the point (design intent)
of the WWW is to be portable; this is cool and I really hate that it is less
and less true. You go to
a WWW site to find some information and some WWW geek makes you
HAVE to download some Media player or other when all you want to do is read
the corporate investment news not hear his "cool" sound track. (Likewise
I could not go to read the MSDN documentation from my friend's Sun workstation
so that I could do some work on her machine.)
On that vane, I hate proprietary WWW protocols of any and all
kinds. Why should I have to code to support 2 or 3 browsers?
What is wrong with having standards and sticking to them? Is the
WWW stuff REALLY that leading edge or is it a case of marketing
BS? In summary, why can't browsers compete on performance rather than on
protocol? I hope that the WWW community can shed the
mentality that using propietary protocols is O.K. The problem is
the "Microsoft Certified and Microsoft Indoctrinated mentality".
Their are lots of people who only know what the Microsoft solution is to
any given problem. (This is a bad thing.)
Of course that taken at the extreme, one would never even use new features
since standards will evolve all the time. But, at least if the new standards
are indeed STANDARDS, they will eventually be supported on the target platform
by someone ... If there is a backward compatibility problem, I can't blame
microsoft for taking their current stand, but I thought HTML comes complete
with a version identifier...? But I'm not an HTML
expert either.
of the WWW is to be portable; this is cool and I really hate that it is less
and less true. You go to
a WWW site to find some information and some WWW geek makes you
HAVE to download some Media player or other when all you want to do is read
the corporate investment news not hear his "cool" sound track. (Likewise
I could not go to read the MSDN documentation from my friend's Sun workstation
so that I could do some work on her machine.)
On that vane, I hate proprietary WWW protocols of any and all
kinds. Why should I have to code to support 2 or 3 browsers?
What is wrong with having standards and sticking to them? Is the
WWW stuff REALLY that leading edge or is it a case of marketing
BS? In summary, why can't browsers compete on performance rather than on
protocol? I hope that the WWW community can shed the
mentality that using propietary protocols is O.K. The problem is
the "Microsoft Certified and Microsoft Indoctrinated mentality".
Their are lots of people who only know what the Microsoft solution is to
any given problem. (This is a bad thing.)
Of course that taken at the extreme, one would never even use new features
since standards will evolve all the time. But, at least if the new standards
are indeed STANDARDS, they will eventually be supported on the target platform
by someone ... If there is a backward compatibility problem, I can't blame
microsoft for taking their current stand, but I thought HTML comes complete
with a version identifier...? But I'm not an HTML
expert either.