From: Pavel Machek <pavel@suse.cz>
To: David Lang <david.lang@digitalinsight.com>
Cc: Jesse Pollard <jesse@cats-chateau.net>,
"Giacomo A. Catenazzi" <cate@pixelized.ch>,
Krishna Akella <akellak@onid.orst.edu>,
Paul Jakma <paul@clubi.ie>,
kartikey bhatt <kartik_me@hotmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Can't X be elemenated?
Date: Tue, 7 Oct 2003 21:16:51 +0200 [thread overview]
Message-ID: <20031007191651.GD610@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.58.0310071206370.19220@dlang.diginsite.com>
Hi!
> > > And yet.. there are times when I need something VERY light weight, and
> > > globally portable. So I started my own for a specific application
> > > where
> >
> > Well, in one of previous mails I said that "one per goal" is the right
> > thing. So it is okay for "small" toolkits to exists, but I do not like
> > qt vs. gtk, because they have identical goals.
> >
> > Anyway, this is off-topic for linux-kernel, and I guess we should end
> > here.
>
> *BSD and Linux have the same goals (at least as close as GTK and QT do),
> does this mean that Linus should not have started writing Linux?
I'm not saying that work on GTK or QT should not have started. I
understand why they did. Still its a pity.
Anyway Linux vs. FreeBSD is completely another situation, because
Linux is clearly dominant. I have no problem with that. But GTK vs. QT
have roughly equivalent usage... Thats bad.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-10-07 19:17 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 14:44 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 ` [OT] " Giacomo A. Catenazzi
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 [this message]
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
2003-09-29 19:45 kartikey bhatt
2003-09-30 8:09 kartikey bhatt
2003-09-30 9:25 ` Matti Aarnio
2003-09-30 9:54 ` Paul Rolland
2003-09-30 13:34 ` Jesse Pollard
2003-09-30 17:50 kartikey bhatt
2003-10-01 4:32 kartikey bhatt
2003-10-01 5:00 ` Tupshin Harper
2003-10-01 15:12 ` Jesse Pollard
2003-10-01 18:27 ` Tomasz Rola
2003-10-02 8:57 ` Helge Hafting
2003-10-02 18:18 ` Herbert Poetzl
2003-10-03 14:30 ` Jesse Pollard
2003-10-02 18:37 ` Erik Steffl
[not found] <BGWr.3eL.7@gated-at.bofh.it>
2003-10-01 8:19 ` Ihar 'Philips' Filipau
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=20031007191651.GD610@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akellak@onid.orst.edu \
--cc=cate@pixelized.ch \
--cc=david.lang@digitalinsight.com \
--cc=jesse@cats-chateau.net \
--cc=kartik_me@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@clubi.ie \
/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
Powered by JetHome