Why do I use Linux?

[Ric Whitney]

Quoting Joseph Sinclair <plug-discuss at stcaz.net>:

> I'd suspect that you use Linux for the same reason many people do.
> Microsoft (all proprietary software really) tells you what you can 
> do, then tells you how you can do it, and charges for the privilege.
> Linux asks what you want, gives you some tools, and says "Innovate".
> Innovation is a natural human instinct, and F/LOSS nurtures that 
> instinct by providing an environment where innovative uses of 
> software, even if that use requires the software to be changed, are 
> allowed and encouraged, sometimes even required.  In a proprietary 
> environment there will always be excessive restrictions to what you 
> can do with the software, because the vendor has a vested interest in 
> limiting your innovation.  The less you innovate, the more often you 
> have to pay them to innovate for you, and the higher their profit 
> margins.  If they can further limit your right to even use what 
> they've created, they can profit even more (think DRM and 
> pay-per-play, RIAA/MPAA drool over that future).
>
> An Example:
> Say you want to connect a new whiz-bang RF transmission device to a 
> handheld computer, and create the "Next Big Thing"(sm) in wireless 
> communications.
> Further suppose that, to make it more flexible, your gadget is 
> software-defined-radio, and the algorithms run on the handheld.
> On Windows, you have to pay Microsoft for a Kernel SDK, pay Microsoft 
> for a "Shared Source" license, and submit to intrusive Microsoft 
> monitoring of your development team akin to a daily Colonoscopy.  
> When you're done, Microsoft will claim all copyright/patent rights to 
> the myriad changes in the Windows Kernel you had to make to get 
> Windows to work with your new gadget.  Just before your gadget is 
> released to market, Microsoft notifies you that you have to ship a 
> custom build of PocketPC to every user, since they've decided not to 
> include your changes in the mainstream release, and you will have to 
> pay MS a ton of $$ per unit for the OEM license to ship that custom 
> version, causing the price of your new gadget to increase 8,000%.  At 
> this point you give up in disgust and, at the suggestion
> of a few engineers, decide to try making your gadget work on Linux instead.
> On Linux, you download the kernel source, load up BitKeeper (you'd 
> use Git or SVK if this was done today) and begin developing the 
> required changes.  In the meantime you sign on to the Kernel mailing 
> list and begin discussing what you need to do to the kernel, and why, 
> with the thousands of experts who work on the kernel every day.  In a 
> surprisingly short time you have the kernel modified to work with 
> your gadget, and it's better because the other kernel developers made 
> some really good suggestions.  You send a patch set to Linus and, 
> after some public discussion and a little tweaking, the next version 
> of the kernel has full support for your new gadget, and any similar 
> gadgets anyone might want to develop in the form of a kernel module.
> Notice how the proprietary vendor forced the developer to do things 
> their way, under their rules, and pay them at every step.  Now notice 
> how Linux not only encouraged you to make your changes (by making the 
> source and tools easy to get and free of charge or other 
> encumbrance), but made it easy to get help, to improve the results, 
> and to provide the resultant improvements to everyone who might be 
> interested in them, so you have less work to do going forward, and 
> can focus on your new gadget and it's software, not the O/S kernel.
> Of course, since the developer in this example did the Windows 
> development first, Microsoft would bring in their legal attack dogs 
> to stop their Linux effort before they submitted the patch set (on 
> the basis that the "Shared Source" license agreement prohibits this 
> kind of crossover development), since the last thing Microsoft wants 
> is more tools that work on Linux but not Windows.
>
> It comes down to the same issue involved in the Massachusetts 
> OpenDocument decision.  You want the right to own the product of your 
> effort, and the right to live free of undue constraint.  The 
> proprietary vendor wants to impose undue constraint at every stage 
> possible, and they want to own the product of your effort, and lease 
> it back to you.  If you accept the proprietary environment, you will 
> pay for the tools to work with, and continue to pay for access to 
> everything you create with those tools, and you may have to give up a 
> lot of privacy (and/or security) to help the vendor enforce their 
> "right" to charge you for access to your own work-product.  The 
> proprietary environment is ridiculously profitable because the vendor 
> now charges for the exercise of basic rights (which cost them
> nothing, and they're basic because they're used all the time, so they 
> can charge you all the time).  If you choose the F/LOSS environment, 
> you may pay for some tools (or may not), but what you produce with 
> those tools is unquestionably yours, and you can do whatever you want 
> with the fruits of your labor, from giving it away to selling it for 
> whatever the market will bear, to just leaving it on a shelf 
> somewhere.
>
> ==Joseph++

Very well said Joseph!  Thank you.
May I create an analogy that I hope will not offend but those inclined 
will pick
up on this analogy.

There was a discussion.  At the head of this discussion were two 
brothers.  One
of the brothers said to his dad, "Let me go and do what you request, 
and I will
make sure everything and everyone is all right when I'm finished. Just give me
all honor for doing this."  The other brother said, "Dad, I want to do 
what you
want me to do, the way you want me to do it.  This way everyone will have a
choice to do things the way they want.  Not everyone will be all right 
when I'm
done, but if they come out all right, they'll be able to share our happiness,
unbridled, unchained, free."

Ric Whitney
Transcend Development
"Producing the next phase of your internet presence"
http://xend.net
Premium Quality Web Hosting
http://xendhosting.com
rw AT xend.net
Net Binder  http://netbinder.net
310-943-6498
602-288-5340