(This is a direct response to O'reilly some sort of perl monopoly?
and (OT troll) New Section: PHP
. Please read those posts for the context in which this meditation is written.)
The Free and Open-Source Software worlds (aka, F/OSS, and yes, they aren't synonymous) are and aren't certain things. Unfortunately, the distinction between those things is often blurred, for various reasons. I'm going to assume that, for most people, the reason is ignorance. Not blind unwilling ignorance, but "I haven't been exposed to the facts" ignorance. So, here's some facts.
- A way to collaborate on software
- A new way of thinking about software
- An attempt to get good quality software into the hands of as many people as possible
- A way of providing the tools to do all of the above
F/OSS is NOT:
- An attempt to deny the profit motive
- An attempt to destroy the copyright or patent process
- An attempt to steal intellectual property (aka IP)
- An attempt to push all IP into the public domain or Creative Commons
Larry (and a few others) own Perl (they have the copyright). Literally, just like I own the shirt on my back. They have chosen to give up a good portion of control normally associated with ownership over Perl, but it is not public domain. Something is public domain if there isn't a specific owner.
As for the profit motive, let's look at a great example - RedHat. RedHat makes a lot of money on Linux. (Last year, they had revenues of almost $200 million dollars.) They do so in four ways:
- You can pay for them to support your Linux installation
- You can pay for them to train your people
- You can pay for a tested Linux distribution that's tailored to your needs (Yes, a given Linux distribution can be sold and Linux is under that "damned viral GPL".)
- You can pay for the RedHat brand
What's the upshot? A lot of companies (including my employer) make a lot of money off of F/OSS. I get paid to write F/OSS that furthers the needs of my employer. F/OSS isn't the enemy of profit ... it just means you have to profit on your work, not your shrinkwrap.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||