|
|
Posted by Matt Clara on 03/24/06 21:04
"Alan J. Flavell" <flavell@physics.gla.ac.uk> wrote in message
news:Pine.LNX.4.62.0603241509260.8011@ppepc62.ph.gla.ac.uk...
> On Fri, 24 Mar 2006, Travis Newbury wrote:
>
> > Alan J. Flavell wrote:
> > > A pity that MSIE plays by totally different rules.
> >
> > This is only true if you assume someone else's rules are the right
> > ones. At the time Desktops were dominated by Microsoft. The makers
> > of the "rules" happened to be on *nix.
>
> I suspect that you're being ironic. Unfortunately there may be many
> readers who know so little history that they might literally believe
> you.
>
> Have a look at
> http://www.w3.org/History/19921103-hypertext/hypertext/WWW/Status.html
> and see if you can discern dominance of any particular OS. NeXT,
> VAX/VMS, IBM VM/CMS, Macintosh, all feature in different ways.
>
> (P.s the claim made in that page that the VM/CMS browser was
> non-existent was not really true. Some of us supported a port of the
> W3 client to VM/CMS: it wasn't very good, but it certainly wasn't
> "nonexistant"(sic) as that document claims. In fact, see
>
http://www.w3.org/History/19921103-hypertext/hypertext/WWW/LineMode/vm-cms/Overview.html
> But that's all a long time ago now)
>
> But the MIME and HTTP specifications are not just a private affair of
> the WWW - they have proper IETF standards-track specifications about
> their behaviour on the Internet. They are carefully defined to be
> rather OS-agnostic. *If* the claim had been true that they were
> unix-centric, do you suppose they would have defined the canonical
> newline representation to be CRLF? Surely it would have been LF
> alone, just as it is in unix?
>
> > Plus look at the bandwidth microsoft is saving the world
> > elmininating that one character. If every HTML page being called
> > world wide was now HTM the savings would be huge!
> >
> > So rather than condeming Microsoft, we should be thanking them and
> > scolding anyone that uses HTML...
>
> I know you're joking, really, but...
>
> We would be entitled to scold /anyone/ who uses filename extensions in
> their URLs. To anyone who takes theory as more important than
> practice, it's clear that they have no business being there at all.
>
> (If you /really/ care about network bandwidth, you should be aware
> that most browsers nowadays support gzip compression, and (x)HTML
> lends itself very well to such compression. You could save file space
> too, in that way).
Yup, Microsoft has never been concerned with the end user's bandwidth. Take
a look at this code I found on the site where I work. It was created by
copying and pasting directly from MS Word to a WYSIWYG editor:
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; mso-list: l1 level1 lfo2;
tab-stops: list .5in"><span style="FONT-SIZE: 12pt; FONT-FAMILY: Arial;
mso-bidi-font-size: 10.0pt; mso-fareast-font-family: 'Times New Roman';
mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language:
AR-SA"><font face="Arial, Helvetica" size="2">To request a Compliance
Inspection, or Contact, please call the EAB Hotline at 866-325-0023 or email
at</font> <a href="mailto:blah at michigan.gov"><font face="Arial,
Helvetica" size="2">Inmanca@michigan.gov</font></a><font face="Arial,
Helvetica" size="2">.</font></span></p>
All that to mark up a single sentence. Amazing.
--
Regards,
Matt Clara
www.mattclara.com
Navigation:
[Reply to this message]
|