public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Definitely unslung
Date: Wed, 6 Jun 2007 21:18:00 -0500	[thread overview]
Message-ID: <001301c7a8aa$12302400$ab00a8c0@tenstac> (raw)
In-Reply-To: <20070607005638.GB14500@grml>

The sad truth is that the best technology doesn't win, this has 
been proven over and over. Truth is the x86 architecture is 
an ugly beast and getting uglier, but the economies of scale
are huge and prior investment in development is what keeps 
it alive. Surely that is precisely why Apple switched to Intel,
the PowerPC is actually superior, so is SPARC and ARM.
Beta was better than VHS video. What isn't better than 
Windoze? Why am I running it right now? Only because 
there are still some things I can't do on linux yet. OS/2 was 
light years ahead of Windows and even RAN windows apps. 
OSX has better prospects (it's based on BSD unix!), and I 
actually think Steve Jobs made the right decision ditching 
PowerPC because Intel compatible is a dime a dozen.  

The iPhone will use ARM ... like almosy anyPhone in the
forseeable future. Perhaps this an example where better 
tech does win. There are more ARM processors running 
than Pentiums right now, just on smaller devices. The wild
thing is that ARM the company does NOT make silicon.
They sell IP ... intellectual property. They have hundreds 
of licensees of ARM IP. You can choose from well over 
a hundred different ARM processors just from Digikey 
alone. This is one reason to be interested in ARM and do
some work with it, there may come a day when ARM 
will actually bring the death of the ugly x86. Intel will have
to design something new or jump on that same bandwagon.
So will AMD. What IBM will do is anybody's guess, same
with Sun, executives at all three are surely squirming right
now.
  
  -- Doug

PS. Then there's the iRack LOL
http://www.glumbert.com/media/irack
  


  reply	other threads:[~ UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Georgina Joyce
 ` C.M. Brannon
   ` Kerry Hoath
     ` Doug Sutherland
   ` Buddy Brannan
     ` Kerry Hoath
       ` Travis Siegel
         ` Buddy Brannan
           ` David Poehlman
             ` Buddy Brannan
               ` David Poehlman
               ` Travis Siegel
                 ` Alex Snow
                   ` Doug Smith
                     ` Gregory Nowak
                     ` Travis Siegel
                       ` Doug Smith
                         ` Travis Siegel
                           ` David Poehlman
                     ` Doug Sutherland
                       ` Doug Smith
                         ` Doug Sutherland [this message]
                       ` Doug Sutherland
                   ` Travis Siegel
                     ` Gregory Nowak
                       ` Travis Siegel
                     ` Luke Yelavich
                     ` Alex Snow
           ` Travis Siegel
         ` David Poehlman
     ` David Poehlman
       ` Alex Snow
     ` Georgina Joyce
   ` Travis Siegel
     ` Buddy Brannan
       ` Travis Siegel
         ` Buddy Brannan
           ` Kirk Reiser
     ` Georgina Joyce
   ` Georgina Joyce
   ` Alex Snow
     ` C.M. Brannon
 ` Doug Sutherland

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='001301c7a8aa$12302400$ab00a8c0@tenstac' \
    --to=doug@proficio.ca \
    --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).