From: "Giacomo A. Catenazzi" <cate@debian.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Lang <david.lang@digitalinsight.com>,
Krishna Akella <akellak@onid.orst.edu>,
Paul Jakma <paul@clubi.ie>,
kartikey bhatt <kartik_me@hotmail.com>,
linux-kernel@vger.kernel.org
Subject: [OT] Re: Can't X be elemenated?
Date: Tue, 07 Oct 2003 14:46:30 +0200 [thread overview]
Message-ID: <3F82B5A6.2000203@debian.org> (raw)
In-Reply-To: <20031007121825.GA323@elf.ucw.cz>
Pavel Machek wrote:
>>Do you want only one distribution for user, one for small companies, one
>>for schools,...? Do you want only one web server implementation? Only one
>>filesystem per task (only one journaling FS)?
>>Are they all "historical accident"?
>
>
> Well, I'm pretty glad there's only one glibc,
only one glibc, but there are some implementation of libc. Also in this list we
discuss about a tiny libc for init process, but you are right, it solve another
problem (be small and simple). But from such discussion I worried to know that
there exist so much implementation of libc.
> and only one http protocol, and only one X protocol.
You speak about protocols (but there are also incompatible extention), but you
know that there exists a lot o toolkit to handle http links...
> And it would be way better if there
> was just one toolkit commonly used on Linux.
better? More efficient yes. But you know... GNU/Linux comunity will start a long
(more years) flameware to choose the best solution, the best protocol,...
so IMHO it is good that we have different toolkits (so I think less flames, more
work). But I agree that in long period we should switch to one toolkit (as we
switched (nearly) all to glibc, xfree86 (but yet a new fork?), gcc(egcs style),...
BTW IIRC the discuttion was about qt and gtk. IIRC the KDE and gnome comunities
are approaching methods and protocols, so in future maybe we will have only one
toolkit, but not to correct an "historical accident" but because evolution.
ciao
giacomo
next prev parent reply other threads:[~2003-10-07 12:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 14:44 Can't X be elemenated? kartikey bhatt
2003-09-29 14:51 ` Leonard Milcin Jr.
2003-09-29 15:05 ` Gábor Lénárt
2003-09-29 15:10 ` Erik Hensema
2003-09-29 15:11 ` Valdis.Kletnieks
2003-09-29 20:56 ` George France
2003-09-29 21:04 ` Erik Bourget
2003-09-29 21:16 ` Erik Steffl
2003-09-29 21:11 ` Diego Calleja García
2003-09-29 22:30 ` bill davidsen
2003-09-30 8:18 ` [OT ]Re: " Helge Hafting
2003-09-30 18:48 ` Paul Jakma
2003-09-30 19:30 ` Krishna Akella
2003-09-30 20:21 ` David Lang
2003-09-30 20:46 ` Krishna Akella
2003-09-30 20:45 ` David Lang
2003-10-07 4:04 ` Pavel Machek
2003-10-07 8:23 ` Giacomo A. Catenazzi
2003-10-07 12:18 ` Pavel Machek
2003-10-07 12:46 ` Giacomo A. Catenazzi [this message]
2003-10-07 12:52 ` Måns Rullgård
2003-10-07 14:34 ` Valdis.Kletnieks
2003-10-07 14:47 ` Jesse Pollard
2003-10-07 15:37 ` Pavel Machek
2003-10-07 19:07 ` David Lang
2003-10-07 19:16 ` Pavel Machek
2003-10-07 20:09 ` jlnance
2003-10-07 18:52 ` David Lang
2003-09-30 21:51 ` J.A. Magallon
2003-10-01 14:54 ` Jesse Pollard
2003-10-01 8:27 ` John Bradford
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=3F82B5A6.2000203@debian.org \
--to=cate@debian.org \
--cc=akellak@onid.orst.edu \
--cc=david.lang@digitalinsight.com \
--cc=kartik_me@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@clubi.ie \
--cc=pavel@ucw.cz \
/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.