From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Paratimer@aol.com
Cc: lm@bitmover.com, adam@yggdrasil.com, linux-kernel@vger.kernel.org
Subject: Re: business models [was patent stuff]
Date: 28 May 2002 16:42:18 +0300 [thread overview]
Message-ID: <1022593339.21314.63.camel@sake> (raw)
In-Reply-To: <50.c105234.2a24c92d@aol.com>
On Tue, 2002-05-28 at 14:51, Paratimer@aol.com wrote:
> In a message dated 5/28/2002 3:55:00 AM Eastern Daylight Time,
> gilad@benyossef.com writes:
>
>
> > On Tue, 2002-05-28 at 01:24, Larry McVoy wrote:
> >
> > > If the free software community is ever going to really compete with the
> > > non-free software community, they simply have to come up with a better
> > > business model than giving it away and trying to make money on support.
> > > It's economics 101 - a free market will go to whomever can provide the
> > > needed service most cheaply. With no barrier to entry, that means as
> > .........^^^^^^^^
> > > soon as the price gets high enough, someone will resell the
> > > product for
> > ..^^^^^^^
> > > less. Which results in razor thin profits, if any at all.
> >
> > Software is not a "product" any more then a lawyer argument in a case is
> > a "product" or an architect plan for a building is a "product".
>
> Actually, a lawyer's argument or an architects plan can certainly
> be work products, and if I hire a lawyer to draw up a contract for
> me or an architect to design a building for me, unless our agreements
> say otherwise, I own the contract or the building plans.
>
Of course you *can*, but do you (or anyone else) actually does this?
AFAIK this is not a very common business model.
Gilad.
--
Gilad Ben-Yossef <gilad@benyossef.com>
Code mangler, senior coffee drinker and VP SIGSEGV
Qlusters ltd.
"A billion flies _can_ be wrong - I'd rather eat lamb chops than shit."
-- Linus Torvalds on lkml
next parent reply other threads:[~2002-05-28 13:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50.c105234.2a24c92d@aol.com>
2002-05-28 13:42 ` Gilad Ben-Yossef [this message]
2002-05-28 14:29 ` kernel 2.5.18 on alpha Oliver Pitzeier
2002-05-28 15:17 ` [patch] " Ivan Kokshaysky
2002-06-04 9:55 ` Oliver Pitzeier
2002-05-30 15:13 ` Oliver Pitzeier
2002-05-30 15:17 ` David Woodhouse
2002-05-29 19:13 business models [was patent stuff] Adam J. Richter
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 3:21 Adam J. Richter
2002-05-29 13:15 ` Alan Cox
2002-05-29 14:13 ` Jonathan Corbet
2002-05-29 16:15 ` Jamie Lokier
2002-05-29 17:29 ` Nicholas Knight
2002-05-31 20:17 ` Perry The Cynic
2002-06-03 10:49 ` Rob Landley
2002-05-28 17:13 Adam J. Richter
2002-05-28 17:52 ` Daniel Phillips
2002-05-28 18:22 ` Alan Cox
2002-05-28 17:23 ` Andre Hedrick
2002-05-29 21:44 ` David Weinehall
2002-05-30 4:51 ` Greg KH
2002-05-27 21:52 patent on O_ATOMICLOOKUP [Re: [PATCH] loopable tmpfs (2.4.17)] Adam J. Richter
2002-05-27 22:24 ` business models [was patent stuff] Larry McVoy
2002-05-27 23:15 ` Karim Yaghmour
2002-05-27 23:31 ` Austin Gonyou
2002-05-28 9:29 ` Peter Wächtler
2002-05-28 13:46 ` Mark Mielke
2002-05-29 8:34 ` Peter Wächtler
2002-05-28 7:53 ` Gilad Ben-Yossef
2002-05-28 8:57 ` Daniel Phillips
2002-05-28 11:30 ` Alan Cox
2002-05-28 10:32 ` Ingo Oeser
2002-05-28 12:28 ` Jonathan Corbet
2002-05-28 18:35 ` Eric W. Biederman
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=1022593339.21314.63.camel@sake \
--to=gilad@benyossef.com \
--cc=Paratimer@aol.com \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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