public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: RE: BrailleNote
Date: Tue, 18 Apr 2000 05:55:34 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0004180551540.3996-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.10.10004180631460.8187-100000@sdf.lonestar.org>

> considered the cost, but I'm sure it's in the $5k + range.  So, why would
> someone pay that kind of money for half a computer.  

I think the reason people are willing to pay this cost is that there isn't
much choice for the functionality. This is the best priced hardware of its
type that I have seen. It should be much more functional then anything
Blazie has come out with. And it is in the $3k to $5k range depending on
how many Braille cells are in the unit. The cost of the computer itself is
negligible when compared to the cost of the refreshable disply cells.

The real mystery is why people still have to purchase the BNS for its
cost. I can't imagine how a 20 year old peice of hardware can be so
expensive. Even knowing they have updated it, they charge new product
prices.

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

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



  reply	other threads:[~ UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 BrailleNote Christopher Moore
 ` BrailleNote Buddy Brannan
 ` BrailleNote Dave Hunt
   ` BrailleNote Christopher Moore
     ` cpt.kirk [this message]
       ` BrailleNote Scott Howell
     ` BrailleNote Buddy Brannan
       ` BrailleNote cpt.kirk
         ` BrailleNote Scott Howell
         ` BrailleNote Christopher Moore
           ` BrailleNote cpt.kirk
             ` BrailleNote RK
               ` BrailleNote cpt.kirk
                 ` BrailleNote craig martin
                 ` BrailleNote Christopher Moore
     ` BrailleNote Dave Hunt

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.21.0004180551540.3996-100000@localhost.localdomain \
    --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).