public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: xconq <xconq7@sources.redhat.com>
Subject: Re: Xconq UI thoughts
Date: Thu, 20 Nov 2003 02:57:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0311192138160.747-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDGEAPGMAB.vanevery@indiegamedesign.com>



> And not to state this unfairly, but there's a developer breeding
> mechanism at work in such things.  People who really value AAA
> production values, and who are capable of producing them, move on and
> find a way to make those things in commercial products.  People who
> don't, generally stay behind in hobbyist freeware projects like Xconq.
> I'd love any pointers to specific exceptions that break the general
> rule.  But from where I sit, the people with the drive and talent to
> produce what you're suggesting, generally aren't available as volunteer
> labor.

Of course this totally overlooks the segment of developers that 
have both the drive and the talent, but have made other career 
choices that they find more fulfilling, __who simply work on a 
project as a hobby in their meager free time.

> > (Programmers love keyboards, but see #4.)
> 
> No, not all of them do.  I hate 'em.

This explains much....

> Infrastructure should be built for people who are *actually* using it,
> as they actually *need* it.

Could it be?! He _finally_ gets it! Now he understands why there 
was no red carpet and royal fanfare waiting for him wrt the 
Windows build process. Amazing, he _finally_ gets it....

  reply	other threads:[~2003-11-20  2:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  2:15 Stan Shebs
2003-11-20  2:26 ` Brandon J. Van Every
2003-11-20  2:57   ` Eric McDonald [this message]
2003-11-20  9:45     ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:49       ` Bruno Boettcher
2003-11-20 10:59         ` Brandon J. Van Every
2003-11-20 11:51           ` Jakob Ilves
2003-11-20 12:05             ` Brandon J. Van Every
2003-11-20 17:57             ` Jim Kingdon
2003-11-20 17:24       ` Eric McDonald
2003-11-20 17:51         ` Eric McDonald
2003-11-21  1:59         ` altruistic VS 2003 Solution files Brandon J. Van Every
2003-11-21  4:17           ` Eric McDonald
2003-11-21  9:02             ` So let's get right to the point Brandon J. Van Every
2003-11-21 23:14               ` Lincoln Peters
2003-11-22  0:06                 ` Why Eric doesn't like my personal style Brandon J. Van Every
2003-11-23 11:13                   ` Mark A. Flacy
2003-11-23 14:22                     ` Brandon J. Van Every
2003-11-22  0:07                 ` So let's get right to the point Brandon J. Van Every
2003-11-21  2:01         ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:31   ` Xconq UI thoughts Andreas Bringedal
2003-11-20 10:37     ` keys and menus Brandon J. Van Every
2003-11-20 10:58     ` Xconq UI thoughts Bruno Boettcher

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.44.0311192138160.747-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --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).