public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Erik Jessen" <ejessen@adelphia.net>
To: "'Jim Kingdon'" <kingdon@panix.com>, <xconq7@sources.redhat.com>
Subject: RE: HW requirements
Date: Sun, 11 Jan 2004 07:25:00 -0000	[thread overview]
Message-ID: <000101c3d815$45825cb0$6401a8c0@Win2k> (raw)
In-Reply-To: <200401110344.i0B3iCq16470@panix5.panix.com>

Based on a few of the last emails, I heard:

a) 24MB is the min.
b) it's an unrealistic min.

So, is anybody even really considering HW resources when actually doing
development?  (other than the general rule of "don't be wasteful")?

I'm just trying to understand the environment Xconq is living in - I
simply don't have any data - I do chip design for a living, not
software.

Erik

-----Original Message-----
From: xconq7-owner@sources.redhat.com
[mailto:xconq7-owner@sources.redhat.com] On Behalf Of Jim Kingdon
Sent: Saturday, January 10, 2004 7:44 PM
To: xconq7@sources.redhat.com
Subject: Re: HW requirements

> How many people use VT100 any more?

One posted to the list just recently.

To me the real questions are not so much "how many users (or potential
users) with this or that hardware/OS/etc" but "is anyone willing to
test xconq on such-and-such setup?" and "is there any benefit to
assuming more memory/cpu/whatever?".  All too often (although
certainly not always) the answer to that last question turns out to be
"no", but one might only notice it when you've done some profiling
and/or other analysis about where the resources are going.


  reply	other threads:[~2004-01-11  7:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07  2:40 New Action: change-type Eric McDonald
2004-01-07  2:47 ` Erik Jessen
2004-01-07  3:30   ` Eric McDonald
2004-01-07  2:51 ` Lincoln Peters
2004-01-07  4:04 ` Hans Ronne
2004-01-07  4:31   ` Eric McDonald
2004-01-07 20:08   ` klaus schilling
2004-01-07 20:17     ` Eric McDonald
2004-01-07 20:26     ` Hans Ronne
2004-01-07 20:47       ` Eric McDonald
2004-01-07 21:22         ` Eric McDonald
2004-01-08  6:28           ` Erik Jessen
2004-01-08 16:26             ` Eric McDonald
2004-01-10  5:49               ` Erik Jessen
2004-01-10 16:42                 ` Eric McDonald
2004-01-10 17:57                   ` Hans Ronne
2004-01-10 18:59                     ` HW requirements Erik Jessen
2004-01-10 19:44                       ` Hans Ronne
2004-01-10 23:31                         ` klaus schilling
2004-01-11  0:25                           ` Erik Jessen
2004-01-11  3:44                             ` Jim Kingdon
2004-01-11  7:25                               ` Erik Jessen [this message]
2004-01-11  7:45                                 ` Eric McDonald
2004-01-11  7:52                                   ` Erik Jessen
2004-01-11 21:19                                   ` Jim Kingdon
2004-01-11  0:31                           ` Hans Ronne
2004-01-08  3:48         ` New Action: change-type Hans Ronne
2004-01-08  4:28           ` Eric McDonald
2004-01-08  6:39             ` Hans Ronne
2004-01-08 16:46               ` Eric McDonald
2004-01-11 16:48 HW requirements Feneric Brown
2004-01-11 17:02 ` Erik Jessen
2004-01-13 10:42   ` Bruno Boettcher
2004-01-11 16:52 Feneric Brown
2004-01-11 18:10 Feneric Brown
2004-01-11 20:05 ` Jim Kingdon
2004-01-11 18:12 Eric W. Brown
2004-01-12 17:19 ` Eric McDonald
2004-01-13 15:59 Eric W. Brown

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='000101c3d815$45825cb0$6401a8c0@Win2k' \
    --to=ejessen@adelphia.net \
    --cc=kingdon@panix.com \
    --cc=xconq7@sources.redhat.com \
    /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).