public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Prader <gnea@rochester.rr.com>
To: Miles Lane <miles@megapathdsl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCE New Open Source X server
Date: Wed, 18 Apr 2001 21:56:03 -0400	[thread overview]
Message-ID: <20010418215602.A9035@rochester.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10104181317440.1478-100000@www.transvirtual.com> <15070.4428.345455.994818@pizda.ninka.net> <20010418192824.A21365@rochester.rr.com> <3ADE2EBD.8A875AE1@megapathdsl.net>
In-Reply-To: <3ADE2EBD.8A875AE1@megapathdsl.net>; from miles@megapathdsl.net on Wed, Apr 18, 2001 at 05:18:05PM -0700

* Miles Lane (miles@megapathdsl.net) uttered:
> Take a chill pill, dude.

i am quite calm. :)

> Dave's questions are perfectly valid.  Obviously, if a bunch of 
> kick-butt programmers want to go off a create a "from-scratch" 
> X11 implementation, please go right ahead!  If it turns out to 
> be great (have rock-solid support for legacy apps, have screaming 
> fast accellerated graphics drivers for all major hardware, support 
> anti-aliased fonts, alpha-blending and so on in a way that is 
> compatible with XFree86 APIs) then, sure, I'll switch over to the 
> new X Server.  Of course, in the seven years that this project 
> will take, XFree86 will have evolved quite a bit.

So you're saying, that unless it _already_ has screaming support from
commercial hardware vendors, then everyone should just support one and
ONLY one type of X server?  There are a lot of other X server projects
out there and different people go about developing them in different
ways.  This whole holier-than-thou attitude about XFree86 that I'm
getting from you and David (not the rest of the XFree86 community, I
know there are bigots out there, but not everyone's a bigot) in general
tends to say to me "hm, these guys really DO have their heads stuck up
their anal cavities! amazing! and now they're trying to say that WE'RE
wrong in our own ways??" it's quite a riot, and i've enjoyed a good
chuckle - but don't get me wrong, i'm not mad at your or David
personally, however the attitudes that you appear to employ seem to
denote a dull sensitivity level around the area of delusionment of
grandeur.  While you may sit there and rebute such claims, your
rebutement would only be further proof of where I am coming from and
thus we understand each other quite perfectly... of course if that is
not the case and someone is holding a gun to your head, forcing you to
make such claims, then please, feel free to express your true feelings,
otherwise, what I have pointed out will be true.

> I suppose the new X Server could jettison support for legacy 
> apps and only support applications written with the latest RAD 
> toolkits.  There might be some value there.  This might also 
> allow the new server to stabilize sooner.

the 'latest RAD toolkits' now THERE'S something decent worth quoting, I
hope you won't mind me doing so. :)  So, going back to the above, and
again, let me know if i'm wrong here, you're saying that in order to
support a decent X server project, there NEEDS to be 'RAD toolkits',
they can't be mediocre, less memory hungry, etc.. they have to be "RAD",
which is quite a vague term.  Perhaps you could elaborate on this,
perferably in private email seeing as how the scope of this topic is
really not fit for this mailing list.

But SERIOUSLY here folks, please take a good look at yourselves for a
second before bothering to take this thread any longer and consider what
I have stated here, is it really worth bashing someone who's just trying
to help out the community as a whole with new ideas that just don't fit
into your paradigm?  Obviously anyone that's going out of their way to
design a new type of X server from the ground up has to have SOME sort
of understanding of various X servers out there, including (but not
limited to) Xfree86, actually KNOWS the design structure, KNOWS where
it's heading, and has decided that they'd like to do something
different, new, from scratch, to go in another direction.  I think Linus
himself did this back in 1991, obviously not with X, but you get the
idea I think.  If not, then don't bother answering cuz it'll just be a
waste of bandwidth (not to say that this particular email isn't, but
once in awhile, it needs to be done. and now it is.)

    .oO Gnea [gnea at rochester dot rr dot com] Oo.
         .oO url: http://garson.org/~gnea Oo.

"You can tune a filesystem, but you can't tuna fish." -unknown

  reply	other threads:[~2001-04-19  1:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 22:02 ANNOUNCE New Open Source X server James Simmons
2001-04-18 22:12 ` David S. Miller
2001-04-18 23:28   ` Scott Prader
2001-04-19  0:18     ` Miles Lane
2001-04-19  1:56       ` Scott Prader [this message]
2001-04-19  2:20         ` Larry McVoy
2001-04-19  3:53           ` Richard Gooch
2001-04-19  3:54         ` Alan Cox
2001-04-19  4:05           ` Scott Prader
2001-04-19 12:06         ` [WAAAY OT]Re: " Mark Salisbury
2001-04-18 23:57   ` Miles Lane
2001-04-19  8:05     ` [Linux-fbdev-devel] " Sven LUTHER
  -- strict thread matches above, loose matches on Subject: below --
2001-04-19 17:16 James Simmons

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=20010418215602.A9035@rochester.rr.com \
    --to=gnea@rochester.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@megapathdsl.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