How can freeware really be free ?

  • Thread starter Thread starter status
  • Start date Start date
S

status

How can freeware be free when it costs the developer $$$ and money to
develop it? So in reality it is not really *pure* freeware now is it?
Costs someone something along the lines.
 
(e-mail address removed) ([email protected]):
How can freeware be free when it costs the developer $$$ and money to
develop it? So in reality it is not really *pure* freeware now is it?
Costs someone something along the lines.

Are we transporting ourselves to Greek philosophers' gatherings now,
gathered about on a grassy hillside, painting these abstracted questions
into the clouds? ;)
 
How can freeware be free when it costs the developer $$$ and money
to develop it? So in reality it is not really *pure* freeware now
is it?
Costs someone something along the lines.

On that train of thought, not much is really free. When I breathe, I
use energy which has to be replenished by eating food. Food costs
money, unless I gather it myself - and I have to spend time on that.
Now, one could argue that if I had no better things to do and actually
enjoyed gathering food (and the food growed wild etc. etc.) then my
breathing would really free.

Ahh... The lovely grassy hillside...

But I isn't so. Not much wild growing food to speak of where I live at
this time of year. And around freezing is a bit cold for my taste to
run around naked.
 
Ahh... The lovely grassy hillside...

But I isn't so. Not much wild growing food to speak of where I live at
this time of year. And around freezing is a bit cold for my taste to
run around naked.

I don't even want to imagine that side of the hill.... ;->

-Jim
 
How can freeware be free when it costs the developer $$$ and money to
develop it? So in reality it is not really *pure* freeware now is it?
Costs someone something along the lines.

Being rather purposely obtuse, aren't you?

The developer chooses what he/she will or won't develop and the
resources involved.

The point being: is it freeware for the *end user*?
 
(e-mail address removed) wondered:

@How can freeware be free when it costs the developer $$$ and money to
@develop it? So in reality it is not really *pure* freeware now is it?
@ Costs someone something along the lines.

All programs "cost some thing" one way or the other. Freeware or not.

Hard Drive Space
[They all take it up in some fashion]

Bandwidth
[To download or upload or for actual use]

Security
[Some programs can compromise your security]

Privacy
[Some programs can compromise your privacy]

Time
[To learn the program. To find out you don't like it. To find out
that you love it. To compare it with other similar programs. To find
out it's Spyware. To find out it's a security or privacy risk. To
download the program]

Cost
[Of being connected to download the program. It might come down to 5
cents for some people or $$ for others. Depending on their connection
costs and where they live.

Electricity
[Unless you have a Chipmunk powered computer it costs you electricity
to run it. BTW if you did have a Chipmunk powered computer it would
still be using electricity, it would just be Bio-electric.]

Systems Tray/Taskbar Space
[Most programs will put an icon in the systems tray or at least in
the taskbar when in use]

Legal Issues
[Look at those people that honestly thought that since they paid for
Kazaa that they could legally download music. I'm sure there are [or
were] some people that use *freeware* P2P programs that think the
same.]

System Stability
[Some programs can really mess up your computer, causing you to lose
data or even worse format]

Medical
[This comes from the injuries sustained when a program doesn't A.
work the way it says it will. B. does everything but what you want it
to. Causing you and the computer to interact in a violent physical
manner repeatedly.]

Alcohol
[You often need this when the Medical doesn't work]

Computer Repair
[You often need this when the Medical and Alcohol fail to work]

The whole freeware definition thing is very very subjective.

Some will only use *pure* freeware
Some will only use Open Source
Some will use anything even crack or warez, for them it's still *free
ware*
Some will use whatever gets the job done.
Some will use Adware

Group V hates Group I
Group F hates Group K
Group G hates everyone not in Group G
Group O loves every one
Group S doesn't care
Group Q hates 3 things from Group J, 1 thing from Group Y, everything
from Group C, is willing to talk about 7 things from Group Z
 
(e-mail address removed) ([email protected]) wrote in
How can freeware be free when it costs the developer $$$ and money
to develop it? So in reality it is not really *pure* freeware now
is it?
Costs someone something along the lines.

rtdos, you have a bad habit of starting new threads each time you
believe you have a new point to make. Could you please please quit
making multiple posts to say exactly the same thing?

<
--
»Q« It's is not, it isn't ain't, and it's it's, not its, if you
mean it is. If you don't, it's its. Then too, it's hers.
It isn't her's. It isn't our's either. It's ours, and
likewise yours and theirs.
-- Oxford University Press, Edpress News
 
Group V hates Group I
Group F hates Group K
Group G hates everyone not in Group G
Group O loves every one
Group S doesn't care
Group Q hates 3 things from Group J, 1 thing from Group Y, everything
from Group C, is willing to talk about 7 things from Group Z

We must all learn to love one another.
 
How can freeware be free when it costs the developer $$$ and money to
develop it? So in reality it is not really *pure* freeware now is it?
Costs someone something along the lines.
There are three types of people who make small software programs.
There is the hobbyist , the philanthropist, and the entrepreneur. The
latter is really in denial . He is really just a hobbyist or a
philanthropist.
 
(e-mail address removed) ([email protected]):
How can freeware be free when it costs the developer $$$ and money to
develop it? So in reality it is not really *pure* freeware now is it?

Bernd Schmitt said:
altruism.

Not quite. Alas, quite often "freeware" turns out to be betaware. I.e.
many software developers use freeware users to beta test their
software. Once the program has been developed enough, thanks to the
numerous beta tester who thought they were using freware, it becomes
payware. Many a freeware program has bitten the dust this way.

Barry
 
Barry said:
Not quite. Alas, quite often "freeware" turns out to be betaware.

Well, not necessarily. There are other reasons to release a software as
freeware.

For example, if you offer a working, but "lite" version of your program
that is sufficient for home use, you make your file format common,
forcing your competitors to somehow include it. That makes your product
more competitive.

Also, if you product is common among private users, it is more
interesting for companies because they do not need to spend money on
education for their employees.

Some people write freeware because they find it thrilling to solve a
problem in an effective way. Others want to improve their chances for
getting a job as programmer - putting good freeware in their resume.

Then, you can use freeware to weaken a competitor who is stronger than
you are in a field or just to bind customers to your company - if MS
offers a IM service in their OS, why get another one?

There are even more points, but I want to have lunch now and therefore
need to stop writing. ;)

bye,

Onno
 
Henry George said:
There are three types of people who make small software programs.
There is the hobbyist , the philanthropist, and the entrepreneur. The
latter is really in denial . He is really just a hobbyist or a
philanthropist.

I would argue that there's another category, in which I place myself.
I have a well-paid day job, in which I develop software used internally
by employees of my department. In my own time, I build software that
helps me to do my job better. If I think it appropriate, I make some of
this extra software publicly available as freeware. I have neither the time
nor inclination to develop my freeware to a full commercial standard,
and I have no interest in writing stuff that I will not use myself.
I put it out there for 2 reasons:
1. To help other people who may find it useful.
2. In the hope that by exposing it more widely, some bugs
may be found, or useful extensions suggested.

Stay tuned for release of an image comparison tool.
 
There are three types of people who make small software programs. There
is the hobbyist , the philanthropist, and the entrepreneur. The latter
is really in denial . He is really just a hobbyist or a philanthropist.

I can't speak to Windows freeware, but that certainly isn't the case in
open-source.

IBM, for example, makes their money selling big iron and the services to
support it. Software isn't IBM's primary product, but nobody's going to
buy the hardware if there isn't any software to run on it. However,
things are evolving so fast now that not even IBM's tens of thousands
of full-time programmers could keep up with all the demands for new
applications or enhancements to the old ones. IBM found their solution
in Linux and open-source software. Linux not only came up from a very
late start but is now surpassing Windows in many areas so there's no
doubt that it's capable of keeping up once it gets there. To move along
development in certain areas that would immediately help sell its
hardware, IBM contributed money, manpower, and source code to the
open-source effort. Rather than making money directly off the software,
they give the fruits of this investment away and make their money from
the demand it generates for mainframes and services. Other large
corporations with similar needs are following IBM's example (Hewlett
Packard comes to mind).

The open-source KDE environment is based on TrollTech's commercial Qt
library. The library is free and open-source to those who write free
applications, but those who would use it to build commercial
applications must purchase a $1500 license from TrollTech. As you might
guess, a programming library has to be exceptionally good to fetch
$1500. Yet, the open-source community gets it for free in return for
exposing a great many technical users to the library and providing a
real-world demonstration of its capabilities to interested corporate
buyers. This is a common model in open source. Sun originally used
StarOffice in a similar manner to advertise their Java language, and now
StarOffice has become a product in its own right.

Free open-source software often grows more than it's designed. The Emacs
editor, for instance, has gotten most of its growth through small code
additions and enhancements, many made by professional programmers using
it to develop their company software. If they need some little feature
that Emacs lacks then they're able, by virtue of its open source code,
to add that feature - something they couldn't do with a closed-source
commercial editor. The programmers are paid because they're working on
company time. The company benefits because its programmers get a
powerful and highly configurable editor which streamlines their work,
and without having to pay $300 or more for a commercial editor for each
and very workstation. The Emacs project benefits because the programmers
feed their enhancements back to the developers for inclusion on later
releases. Aside from the obvious altrusitic motives, their incentive for
giving away their enhancements is that if the changes become part of the
official editor then they won't have to re-implement all those
enhancements every time they upgrade to a new version of the editor.

Open source demoware tends to be so much less crippled than Windows
demoware that I think one could be justified in calling it freeware. The
Sniff+ "source code engineering tool" limits its personal-use edition to
200 files per project, which is nicely chosen to be more than enough for
a home user yet a bit confining for multi-programmer corporate software
development. The corporate version sells for between $1,000 and $3,700
so again home users get a very, very nice product for free and the only
limitation is on something we don't need anyway.

TheKompany.com enhances existing open-source software and sells the
enhanced versions plus their source code. They've been around for a few
years now and their product line just keeps expanding, so they must be
doing something right. Rather than being a deliberately crippled version
of the commercial version, the "demo" version of TheKompany's
enhancements is an application that was meant by its developers to be
complete in its own right. TheKompany just polishes it up a little and
adds some extra features of their own. I hear rumors that they're
experimenting now with some products where their enhancements involve
external programs or libraries that don't fall under the GPL - you can
download the pre-compiled binaries for free but must pay to get the
proprietary source code.

Although designed to be cross-platform, the Apache web server was
initially funded by businesses that needed a Unix-based web server, as
well as by companies that sell the systems the software runs on. Running
a business on the web also requires a database and scripting languages,
so these free applications are also funded and/or partially staffed by
web businesses and their hardware vendors. And since having a good
browser encourages people to spend time on the web looking at things to
buy, you'll also find some of these companies funding Mozilla, Firebird,
Galeon, Konqueror, etc.

In the office, a few large corporations and a great many smaller ones
don't feel well-served by Microsoft's forced upgrades, new licensing
schemes, extortionate prices, abuse of data lock-in to force customers
to cave in to these things, lack of security, and/or overall lack of
repsonsiveness to unusual needs. They've banded together to fund or
contribute code and manpower to linux, KDE, Gnome, Mozilla, OpenOffice,
etc., all of which are given away for free but are already providing a
big pay-off in other ways.

As for the "hobbyists", a great many unpaid open-source contributors are
professional programmers. On the job, a professional programmer is
somewhat like a creative artist who spends 60 hours a week on a job
where he is told what he will paint, what colors he will use, how large
his canvas may be, and which brushes and techniques he's allowed. It's
only at home that he can finally create what *he* wants to, the way *he*
wants to do it. Corporate programmers usually don't have the time to
start selling software at home but like all artists they want other
people to appreciate their work, so the finished application is released
as open-source. Just incidentally this gains name-recognition for the
programmer among programmers who work for other companies, and exposes
his work for them to show to potential new bemployers.

Some good free software comes out the University environment, too, where
open-source projects provide advanced students with a hands-on
development experience in a large multi-developer project and in return
the open-source community gets some great software. The FreeBSD
operating system that I love so much has its roots at the University of
California at Berkely. The academicians working on the BSD's include
some of the best computer-science people in this country. Their
advanced students working on Master's degrees or a Phd thesis in
computer science make contributions as a learning exercise, while the
professors work on it to keep their hands in or as the basis of an
academic paper. The BSD's have become so popular that other Universities
and parts of the private sector now contribute.

In all of these cases the software is given away for free, yet the
contributors reap rewards. In some cases giving away the software is
what ALLOWS the contributor to realize a benefit.
 
Back
Top