From: Miles Lane <miles@megapathdsl.net>
To: Scott Prader <gnea@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCE New Open Source X server
Date: Wed, 18 Apr 2001 17:18:05 -0700 [thread overview]
Message-ID: <3ADE2EBD.8A875AE1@megapathdsl.net> (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>
Scott Prader wrote:
>
> * David S. Miller (davem@redhat.com) uttered:
> >
> > James Simmons writes:
> > > The Linux GFX project grew out the need for a higher performance X
> >
> > And this specific functionality is?
> >
> > I think this is not a worthwhile project at all. The X tree, it's
> > assosciated protocols and APIs, are complicated enough as it is, and
> > the xfree86 project has some of the most talented and capable people
> > in this area. It would be a step backwards to do things outside of
> > xfree86 development.
> >
> > If the issue is that "things don't happen fast enough in the xfree86
> > tree", why not lend them a hand and submitting patches to them instead
> > of complaining?
>
> You see, it's people like you that actually further along projects such
> as that.. "oh, it'll never work! blahblahblah!" well gee, X _has_ been
> around for years....... but so's microsoft........ so we've all gotten
> into this paradigm that linux is THE end solution for microsoft users...
> got news for ya bud, Linux is great, it's dope, but quite frankly, if u
> put all yer eggs in one basket, you become blind to everything else....
> and bill gates likes that......... but WAIT! someone ELSE comes along with an
> open project.... and what do you do? u take a hateful stance to it... do
> we see a pattern here? you'd have to be pretty blind not to.
Take a chill pill, dude.
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.
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.
Miles
next prev parent reply other threads:[~2001-04-19 0:18 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 [this message]
2001-04-19 1:56 ` Scott Prader
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=3ADE2EBD.8A875AE1@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=gnea@rochester.rr.com \
--cc=linux-kernel@vger.kernel.org \
/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