From: Stewart <bdlists@snerk.org>
To: Glynn Clements <glynn.clements@virgin.net>
Cc: linux-admin@vger.kernel.org
Subject: Re: Rant [Was: Re: changing color depth in XFree86]
Date: Sun, 20 Apr 2003 11:21:17 -0400 [thread overview]
Message-ID: <3EA2BAED.2030308@snerk.org> (raw)
In-Reply-To: <16033.55677.468295.618116@cerise.nosuchdomain.co.uk>
Glynn Clements wrote:
>>Then the applications will have to remove their legacy code and catch up
>>with the needs of the users, rather than the programmers.
>
> Oh right; we'll just re-write all of the existing X applications and
> libraries. No problem.
Melodrama isn't going to help your case, I dare say.
>>Actually, the same is true of resizing the root window; however, fewer
>>applications actually care about that and, for those which do, any
>>failures are likely to be less critical.
>
> Few applications (except window managers) are concerned with the
> screen dimensions, and most of those which are will exhibit relatively
> minor faults if the dimensions do change. The real problem is changing
> the *depth*.
So it's not going to be done because it's "hard"?
Perhaps what I've been saying all along is true; OSS really isn't ready
for prime-time desktop use.
If you're going to claim that the world's most revolutionary programming
model is fundamentally flawed because it won't tackle "hard" problems -
problems which are already overcome by all of their closed-source
bretheren - then just come out and say it.
Or are you going to find a better reason why this is a bad idea?
> I'm a long-time Linux user/admin/programmer who has progressively
> become more sceptical of both Linux and free software generally;
> primarily because of a growing tendency to sacrifice important factors
> such as compatibility (both with previous versions and with real
> Unix/X11 systems) in favour of non-critical features and gimmicks.
>
> Every time that I hear the Slashdot crowd enthusing over the fact that
[...]
And every time I hear a legacy supporter throwing the "Slashdot crowd"
out as if it were a valid argument, I roll my eyes.
> such-and-such now has an animated alpha-translucent drop-shadowed OK
> button I just wonder which rational property was sacrificed for that
> piece of nonsense. Performance? Reliability? Portability? Memory
> consumption? "Who cares? - we have animated alpha-translucent
> drop-shadowed OK buttons, yay!"
We're talking about the X server, not KDE/GNOME. Focus.
>>Changing resolution on the fly has come to be expected from
>>any modern desktop environment.
>
> That sounds like "Windows has it, therefore we should".
No, actually, it means that these are desired (nay, required) features
for many settings, and we don't have it.
>>It's taken far too long, IMO, for XFree86.Org to catch up and
>>implement such functionality in their server.
>
> When it comes to breaking compatibility, the longer they leave it the
> better.
Compatability at the cost of being ten years obsolete, merely for the
sake of compatability, is ridiculous.
next prev parent reply other threads:[~2003-04-20 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 17:48 changing color depth in XFree86 Barry Gamblin
2003-04-17 20:23 ` Glynn Clements
2003-04-19 4:10 ` Stewart
2003-04-19 13:42 ` Glynn Clements
2003-04-19 15:55 ` Stewart
2003-04-19 23:19 ` Rant [Was: Re: changing color depth in XFree86] Glynn Clements
2003-04-19 23:42 ` Bill Sneed
2003-04-20 15:21 ` Stewart [this message]
2003-04-20 14:17 ` changing color depth in XFree86 terry white
2003-04-20 15:11 ` Stewart
2003-04-20 15:52 ` terry white
2003-04-20 23:24 ` Stewart
2003-04-21 1:36 ` terry white
2003-04-21 4:44 ` Stewart
2003-04-21 7:04 ` terry white
2003-04-21 16:34 ` Milan P. Stanic
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=3EA2BAED.2030308@snerk.org \
--to=bdlists@snerk.org \
--cc=glynn.clements@virgin.net \
--cc=linux-admin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.