aRts vs JACK
stefan at space.twc.de
Mon Feb 24 13:17:19 GMT 2003
On Sat, Feb 22, 2003 at 02:18:14PM -0800, Neil Stevens wrote:
> On Saturday February 22, 2003 01:58, Matthias Kretz wrote:
> > On Saturday 22 February 2003 23:06, Neil Stevens wrote:
> > > Non-KDE apps are irrelevant to KDE's choice of system, and KDE apps
> > > are required to do things the KDE way.
> > They're not because a KDE user might want/need to use a non KDE program.
> It's already possible to add new output drivers to artsd. There is no
> reason to change anything else in aRts if that is all you want.
You're right. From the _theoretical_ point of view there is no reason for us
to do anything at all. After all people can send us patches for about
everything they don't like, or even get an CVS account themselves and do the
However, from the _practical_ point of view things look different:
(a) a sound server implementation costs resources: disk space, cpu time,
compile time, download time
(b) thus having two sound servers, or even one, might not be what some users
(c) our task is to do what our users need
I don't identify to the degree that I want to harm anybody who doesn't only
use KDE applications, and help anybody who only uses KDE applications. I want
to help people with free software. If they are using GNOME, they are as
important for me than if they are using KDE. If they are using OpenBSD, they
are as important for me than if they are using Linux.
Adding CSL support to KDE right now seems to me the right thing to do. It does
not disturb people using aRts (because things will continue to function exactly
as they do now), but it helps people not using aRts. And doesn't cost much to
-* Stefan Westerfeld, stefan at space.twc.de (PGP!), Hamburg/Germany
KDE Developer, project infos at http://space.twc.de/~stefan/kde *-
More information about the kde-multimedia