public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: GUIs (was Re: A comment on Slashdot)
Date: Tue, 11 Apr 2000 11:11:12 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10004111100080.2624-100000@rocky> (raw)
In-Reply-To: <Pine.LNX.4.21.0004111259410.29786-100000@neptune.res.wpi.net>

There are two uses for gifs as spacers. One is to replace the standard
rule with a graphical one. This takes very little bandwidth and can add to
the overall appearance of the page. I think it would be best to put in two
quotes here. (But that is assuming the person is bothering to put in alt
text.)

Recently there have been some who uise a gif to eat up space on the page
so that the text is made to look the way they want it. This is disgusting
abuse of bandwidth. I class it along with those reprobate companies that
make the first page a huge graphic that requires at least 800X600
resolution to display. They should have their web pages deleted and cattle
prods taken to their ... (Well I guess I might be getting out of hand
here, but probably not.)

Really, part of the problem on the web today is too much emphasis on looks
and not enough on content. The web is not print media, and many firms
can't grasp that fact. Perhaps we could come up with a protocol for
p[laces that make graphics that don't convey anything. It is one thing to
show me a picture of someone. Or to give me a drawing or map. But to have
a stupid logo blown to the size of my screen is bothersome.

Maybe search engines could be modified to not list these sites since they
don't have content.

Kirk Wood
Cpt.Kirk@1tree.net
------------------

Why can't you be a non-conformist, like everybody else?



  reply	other threads:[~ UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 A comment on Slashdot that concerns me Martin G. McCormick
 ` GUIs (was Re: A comment on Slashdot) cpt.kirk
   ` Janina Sajka
     ` cpt.kirk
       ` Mike Gorse
         ` cpt.kirk [this message]
       ` Janina Sajka
         ` cpt.kirk
           ` Scott Howell
           ` Janina Sajka
             ` cpt.kirk
               ` Victor Tsaran
                 ` cpt.kirk
                   ` Victor Tsaran
                     ` cpt.kirk
                       ` Matthew Campbell
                   ` Janina Sajka
 ` A comment on Slashdot that concerns me Tommy Moore
 GUIs (was Re: A comment on Slashdot) Martin G. McCormick
 ` Christopher Moore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.10.10004111100080.2624-100000@rocky \
    --to=cpt.kirk@1tree.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).