From: Tim McNamara <timmcn@bitstream.net>
Subject: Re: What the next machine will be like after iMac.
Date: 07 Nov 2003 08:33:42 -0600 [thread overview]
Message-ID: <m2ekwks0xl.fsf@localhost.bitstream.net> (raw)
In-Reply-To: y44vfpwznw5.fsf@nestle.ai.mit.edu
Don Saklad <dsaklad@nestle.ai.mit.edu> writes:
> You want to wait for the next design for a machine to be made
> available before buying a new computer. What might the next machines
> be like?... What are the rumors about what the next mahines will be
> when the latest iMac now is considered passe?...
>
> This might be considered directed to Apple Computer users.
And might be more appropriately directed to comp.sys.mac.*
As a long-term Mac user (since 1986) and recent Emacs convert (thanks
to OS X and also to Andrew C.), my guess is that the "future" machine
will be a laptop with a wireless connection to a large flat panel
desktop display, as well as wireless networking, wireless mouses,
wireless storage, wireless keyboard, etc. Look to see your power cord
being the only wire connected to your computer. And look to see this
design on the market within the next two years, at the high end with
dual G5 processors.
A better question for this newsgroup is "what's the future of Emacs?"
next prev parent reply other threads:[~2003-11-07 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 6:35 What the next machine will be like after iMac Don Saklad
2003-11-07 9:05 ` Juri Linkov
2003-11-07 17:29 ` Dan Anderson
[not found] ` <mailman.5.1068233198.2005.help-gnu-emacs@gnu.org>
2003-11-08 7:07 ` Juri Linkov
2003-11-09 18:10 ` Dan Anderson
2003-11-10 7:05 ` Arjan Bos
2003-11-11 6:32 ` Lars Brinkhoff
2003-11-11 10:28 ` Oliver Scholz
2003-11-07 14:33 ` Tim McNamara [this message]
2003-11-07 15:17 ` Stephen H. Westin
2003-11-07 19:50 ` Ola Nilsson
2003-11-07 19:57 ` Barry Margolin
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ekwks0xl.fsf@localhost.bitstream.net \
--to=timmcn@bitstream.net \
/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).