From: "Henning P . Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [LONG RANT] Re: Linux stifles innovation...
Date: Sat, 17 Feb 2001 20:15:39 +0100 [thread overview]
Message-ID: <20010217201539.B13970@forge.intermeta.de> (raw)
In-Reply-To: <96lrau$dcd$1@forge.intermeta.de> <200102171337.f1HDbwh13232@flint.arm.linux.org.uk>
In-Reply-To: <200102171337.f1HDbwh13232@flint.arm.linux.org.uk>; from "Russell King" on Sat, Feb 17, 2001 at 01:37:58PM
On Sat, Feb 17, 2001 at 01:37:58PM +0000, Russell King wrote:
> Henning P. Schmiedehausen writes:
> > But at least I would be happy if there would be a printing
> > engine that is entirely open source and all the printer vendors can
> > write a small, closed source stub that drives their printer over
> > parallel port, ethernet or USB and give us all the features, that the
> > Linux _USERS_ (and these are the people that count) want.
>
> Speaking as a Linux _USER_, if this happens, can I get said print
> engine working on my ARM machines with these closed source drivers?
>
> Can Alpha users get this print system working? Can Sparc uses
> get it working? What? I can't? They can't? Well, its no good to
> me nor them.
Maybe not. But you can use this print engine API to pay anyone to
write a driver for you. What you just said, is exactly my point. You
said:
"If a company does not write a driver which works on all hardware
platforms in all cases and gives us the source, then it is better,
that the company writes no drivers at all."
"If I can't force a company to write a driver for everyone, then I
don't want to write them any driver at all."
IMHO you're like a spoiled kid: "If I can't have it, noone should have it".
> You've just made the system x86 specific. Well done, thats a step
> backwards, not forwards.
No. Some Linux users got a driver that works as well as the drivers
for another OS. This is good for Linux. And all Linux users and
developers got an open, stable API, which is supported by big printer
vendors and enables everyone to write good drivers.
If you need a printer driver for the ARM, you're able to approach the
company XXX and either pay for an ARM specific driver (and they will
listen to you because they already have made a driver for another
Linux platform, learned that they can make money with Linux software
and have experience with driver(s) for Linux. And it will be just a
recompile most of the time).
> Ah, golly, I'll just have to throw my ARM machines away because
> we have some critical parts of the system which are closed source.
We're talking about a driver. If Company XX won't sell it to you for
your architecture, it's their right to do so. There is software that
I've written that you might want to have, too. If I chose not to sell
it to you, what do you do? You can say "company XX sucks" and buy an
equal product with an ARM driver from YY which listens to you. _THAT_
is IMHO open. Not forcing everyone to comply with your ideology.
> > But even if there is such an engine written for Gnome or KDE, some
> > really ingenious "free software advocate" will slap a "must not be
> > used with any kind of non-GPL driver" on it...
>
> Good. I build the stuff to work on my ARM machines.
Can you get a Legato Networker Client for Linux-ARM? Can you get one for
Linux-MIPS? Why? Because someone payed for the port.
> They don't work on ARM though, do they? Gee, I guess ARM Ltd ought to
> stop my contract because what use is an ARM kernel without everything
> else to go with it?
>
> For me, closed source is _REALLY_ bad news. _EXTREMELY_ bad news.
> It 100% prevents me from doing stuff.
No. It means, that for some programs, in order to have them, you have
to pay. That is fine. There ain't no such thing as a free lunch. You
may, of course, chose not to pay, but then you may not be able to use
a certain program.
Look, I'm willing to pay money for the whole M$ Office Suite on
Linux. Yes. I would give billg gladly a big chunk of my money to get
this application suite on Linux. Not a copy or a "just almost like M$
Office". But the real thing. The real "M$ Office 2k" suite for Linux.
Can I? No. Because M$ chose not to offer its product for Linux. Bad
for me. It means, that I can not get parts of my work done on Linux.
Can I buy AutoCAD? Photoshop? Quicken? Outlook? Visio? Not look alikes
or clones or "almost as good as". But the real thing with the same
support as on Windows. I can for the Mac. Why can't I for Linux?
Because IMHO some companies shy away from the aggressive and sometime
openly hostile behaviour of the Open Source community ("If you don't
support your application on Linux/SPARC with an B/W framebuffer, you
suck. Go away") towards commercial companies. ("If you don't support
Gnome 1.0 but just KDE 2.1, you suck. Go away"). And billg laughs and
just points the confused companies towards the "stable" and "easy to
use" M$ OS.
And the volatile APIs which are immature in some points (Font handling.
Printer support. Color handling. Same things all the time. But displaying
the results of your work and printing them onto paper is for many
people the most important thing. And frankly, Linux sucks here).
In your opinion, it is better, that I can't get some programs at all
than paying money for them.
In my opinion, I prefer to get it at least for i386/Linux than not to
get them at all. Because if I can't get them for i386/Linux, I must
get them for i386/Windows. Because I need a specific application.
Not a specific OS architecture.
> Its really good that the Linux community is so open.
So tolerate the fact that some companies chose to release a program as
closed source for only one Linux platform. It is better than not
releasing at all.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2001-02-17 19:16 UTC|newest]
Thread overview: 148+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 17:49 Linux stifles innovation fsnchzjr
2001-02-15 17:55 ` Stephen Frost
2001-02-15 18:04 ` Mark Haney
2001-02-15 19:49 ` David D.W. Downey
2001-02-15 20:20 ` Alan Olsen
2001-02-15 20:42 ` dave
2001-02-15 21:17 ` Richard B. Johnson
2001-02-15 20:43 ` [OTP] " David D.W. Downey
2001-02-15 22:31 ` Bill Wendling
2001-02-15 22:37 ` William T Wilson
2001-02-16 12:45 ` Rik van Riel
2001-02-16 15:10 ` James Sutherland
2001-02-16 16:02 ` Mark Haney
2001-02-16 16:26 ` David Woodhouse
2001-02-16 16:30 ` Mark Haney
2001-02-16 19:23 ` David D.W. Downey
2001-02-16 20:18 ` James Sutherland
2001-02-17 0:03 ` Carlos Fernandez Sanz
2001-02-17 0:35 ` Dan Hollis
2001-02-17 0:41 ` Michael H. Warfield
2001-02-17 1:52 ` Dan Hollis
2001-02-17 2:20 ` XOR [ was: Linux stifles innovation... ] David Relson
2001-02-17 2:32 ` Dan Hollis
2001-02-17 8:16 ` Jonathan Morton
2001-02-17 13:16 ` David Relson
2001-02-17 18:12 ` brian
2001-02-18 2:01 ` Dan Hollis
2001-02-17 9:08 ` Linux stifles innovation James Sutherland
2001-02-17 12:45 ` Henning P. Schmiedehausen
2001-02-17 9:05 ` James Sutherland
2001-02-17 0:04 ` LA Walsh
2001-02-16 9:26 ` Helge Hafting
2001-02-16 9:36 ` James Sutherland
2001-02-16 12:44 ` Helge Hafting
2001-02-16 17:40 ` Joseph Pingenot
2001-02-16 14:25 ` Andrew Scott
2001-02-16 19:48 ` Jesse Pollard
2001-02-16 22:27 ` Dennis
2001-02-16 22:20 ` Alan Cox
2001-02-17 12:37 ` [LONG RANT] " Henning P. Schmiedehausen
2001-02-17 13:37 ` Russell King
2001-02-17 19:15 ` Henning P . Schmiedehausen [this message]
2001-02-17 22:03 ` Felix von Leitner
2001-02-18 11:54 ` Henning P. Schmiedehausen
2001-02-18 12:26 ` Henning P. Schmiedehausen
2001-02-18 13:43 ` Russell King
2001-02-18 9:27 ` Russell King
2001-02-17 19:20 ` Jacob Luna Lundberg
2001-02-18 1:06 ` Peter Samuelson
2001-02-18 4:15 ` Ben Ford
2001-02-17 18:48 ` Jonathan Morton
2001-02-19 9:24 ` Helge Hafting
2001-02-19 10:53 ` Werner Almesberger
2001-02-19 11:07 ` Jeff Garzik
2001-02-19 11:28 ` Nicholas Knight
2001-02-19 11:36 ` David Lang
2001-02-19 12:53 ` Nicholas Knight
2001-02-19 11:47 ` Jeff Garzik
2001-02-19 12:57 ` Nicholas Knight
2001-02-19 12:00 ` Werner Almesberger
2001-02-19 12:15 ` Henning P . Schmiedehausen
2001-02-19 16:04 ` Paul Jakma
2001-02-19 16:07 ` Alan Cox
2001-02-19 14:15 ` Jes Sorensen
2001-02-20 23:39 ` Brian May
2001-02-19 11:59 ` Henning P . Schmiedehausen
2001-02-19 13:11 ` Werner Almesberger
2001-02-19 14:07 ` David Howells
2001-02-19 14:55 ` Jeff Garzik
2001-02-19 15:53 ` Mikulas Patocka
2001-02-19 16:26 ` Jeff Garzik
2001-02-19 19:11 ` The lack of specification (was Re: [LONG RANT] Re: Linux stifles innovation... ) Mikulas Patocka
2001-02-19 20:02 ` Eric W. Biederman
2001-02-19 20:17 ` Albert D. Cahalan
2001-02-19 21:18 ` Mikulas Patocka
2001-02-19 21:34 ` The lack of specification Russell King
2001-02-19 21:47 ` Eli Carter
2001-02-19 15:58 ` [LONG RANT] Re: Linux stifles innovation Richard B. Johnson
2001-02-19 16:14 ` Jeff Garzik
2001-02-19 16:26 ` Alan Cox
2001-02-19 21:57 ` Keith Owens
2001-02-19 19:27 ` Andre Hedrick
2001-02-17 16:54 ` Francois Romieu
2001-02-16 22:31 ` Dan Hollis
2001-02-16 22:51 ` David D.W. Downey
2001-02-16 22:59 ` Linux stifles innovation... [way O.T.] John Cavan
2001-02-16 23:07 ` Linux stifles innovation Mike A. Harris
2001-02-16 23:45 ` Matt D. Robinson
2001-02-16 23:46 ` Mike A. Harris
2001-02-17 0:15 ` Matt D. Robinson
2001-02-17 0:34 ` Werner Almesberger
2001-02-17 0:54 ` Matt D. Robinson
2001-02-17 1:58 ` Werner Almesberger
2001-02-17 12:41 ` Henning P. Schmiedehausen
2001-02-17 17:51 ` Robert Read
[not found] ` <Pine.LNX.3.96.1010217145415.31128A-100000@orion.hq.dalalu.fr>
2001-02-17 18:40 ` Henning P . Schmiedehausen
2001-02-16 23:33 ` Hristo Doichev
2001-02-17 0:01 ` Alan Olsen
2001-02-17 0:10 ` rjd
2001-02-17 1:34 ` Neal Dias
2001-02-17 2:05 ` Augustin Vidovic
2001-02-17 12:46 ` Henning P. Schmiedehausen
2001-02-17 13:13 ` Roeland Th. Jansen
2001-02-21 23:00 ` Dr. Kelsey Hudson
2001-02-21 23:17 ` Augustin Vidovic
2001-02-22 1:08 ` Dr. Kelsey Hudson
2001-02-22 0:09 ` Jonathan Morton
2001-02-22 0:21 ` Alan Cox
2001-02-23 12:14 ` Wakko Warner
2001-02-23 12:31 ` David Weinehall
2001-02-27 8:48 ` Geert Uytterhoeven
2001-02-17 7:20 ` Mike Pontillo
2001-02-17 16:11 ` [OT]Re: " Gregory Maxwell
2001-02-17 7:39 ` Vesselin Atanasov
2001-02-17 19:08 ` Dennis
2001-02-17 19:08 ` Mohammad A. Haque
2001-02-17 20:47 ` Alan Cox
2001-02-24 21:11 ` Dennis
2001-02-24 21:06 ` Alan Cox
2001-02-17 19:11 ` Dennis
2001-02-17 19:36 ` Francois Romieu
2001-02-17 20:48 ` Alan Cox
2001-02-17 19:24 ` Dennis
2001-02-17 19:38 ` Dennis
2001-02-17 20:01 ` Michael Bacarella
2001-02-17 20:11 ` James A. Sutherland
2001-02-17 19:56 ` Linux stifles innovation... [way O.T.] Dennis
2001-02-17 20:28 ` Michael H. Warfield
2001-02-18 11:25 ` Henning P. Schmiedehausen
2001-02-18 15:32 ` John Cavan
2001-02-18 0:13 ` Gerhard Mack
2001-02-17 20:05 ` Linux stifles innovation Dennis
2001-02-17 20:05 ` James A. Sutherland
2001-02-17 20:14 ` Michael H. Warfield
2001-02-18 10:57 ` Henning P. Schmiedehausen
2001-02-17 20:28 ` Alan Olsen
2001-02-21 23:48 ` Dr. Kelsey Hudson
2001-02-17 22:07 ` Felix von Leitner
2001-02-17 20:08 ` Dennis
2001-02-17 20:22 ` Michael H. Warfield
2001-02-17 20:41 ` Gregory Maxwell
2001-02-18 10:59 ` Henning P. Schmiedehausen
2001-02-18 21:02 ` Bob Taylor
2001-02-17 22:38 ` Andre Hedrick
2001-02-17 23:07 ` Michael H. Warfield
2001-02-18 15:20 ` Stefan Smietanowski
2001-02-18 0:51 ` Peter Samuelson
2001-02-16 17:25 ` Byron Albert
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=20010217201539.B13970@forge.intermeta.de \
--to=hps@intermeta.de \
--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