Notice the use of the word "relative" in my very first phrase.
For the rest, you hair-splitting is unconvincing. While different in different contexts,
freedom, capability and need are not unrelated. You should, in fact, be capable of
understanding the entire operation of proprietary software just by disassembling the code.
After all these are instructions to a CPU. Whether you have the legal freedom to do that or
whether the simple possibility of doing this constitutes freedom to modify it once you
understand it in its entirety are entirely separate from your capability to understand the
opcodes. Of course you would argue that this is not true freedom because you can't make
modifications in your preferred form (source code) and the APIs are unpublished, but then you
could just be called lazy: sucks being you if the "code" isn't available in your preferred
form or if you have to disassemble the entirety of the underlying layers to make your program
work. But it remains that in your basement you are *relatively* "free" to do these things.
With regards to your car example, then you're wrong. Sure I am free to bring my car to any
mechanic I want. Much like any regular user is free to bring their computer to whichever
computer repair store they want. But at the end of the day replacement parts (whether they are
software parts or car parts) are going to have to conform to interfaces which are of no choice
to you. And sometimes, in some key car components, you have no choice but to buy the original
manufacturer's parts, regardless of who's repairing your car. In that specific case, arguing
whether spending the appropriate amount of time to reverse engineer said part makes you
"capable" or "free" is really silly. At the end of the day you just want the car to work.
That's what normal users want from software.
With regards to hardware, then you either didn't understand what I wrote or it serves you to
deform it. The fact is you have no access to the vhdl or whatever "code" was used by the
manufacturer to create the chips you use. In fact while you are "free" to change the chips on
your motherboard, most users aren't really capable of doing that, especially since that would
mean have to reverse-engineer the rest of the board so that the replacement fits perfectly.
Much like the disassembly example above: you are "free" but you likely won't take the time and
don't have the proper equipment, so you aren't really "capable" of doing it in a reasonable
time-frame and, in the end, you aren't really free. Nor are you "free" to uncap a chip,
replace the silicon and "fix" or hack it. Your only freedom then is to ditch the hardware and
use something else. Again, I am totally on the spot of saying with some degree of confidence
that *all* free software advocates use unfree hardware and see no problem with that
whatsoever.
Informing users that they have no "freedom" to have their software modified or fixed has no
bearing on the fact that most users wouldn't consider that such "capability" is any more
important than the "capability" for an auto-mechanic to hack their breaks. It might be of
interest to car mechanics amongst themselves, but not their customers.
There is, as a reply to your post rightly points out, some truth to the assertion that there
is a difference between software and the rest of the wares created by humans. That I agree
with, and that's why I've put a lot of the software I did under the GPL. The intangible yet
tangible nature of software does give it properties unlike other embodiments of human thought.
Personally I've found it astounding that our daily lives are controlled by software that only
a handful have vetted. Surely there's a moral argument to be made about making such code
available for all to see.
Regardless of software's special properties, though, it remains that users have little use for
the freedom granted to them by free software. Only the capabilities made available to them by
software matter. And that's why free software will continue to be chosen out in favor of
proprietary software because capability comes before freedom. Having a free car with no seats
is interesting, but it doesn't provide me with the capability to answer my need to go from
point A to point B.
Karim Yaghmour
Founder and CEO
Kryptiva inc.
GNU/Linux World Domination for the Wrong Reasons (Datamation)
Posted Mar 12, 2008 6:16 UTC (Wed) by Duncan (guest, #6647)
[Link]
Thanks to both of you in this thread. I can't say where I come down on
this particular debate, but it has certainly provided food for thought,
giving at least me an opportunity to examine both the general debate and
my own thoughts on the matter in more depth than normal.
And yes, I think it's important, so much so that my NNTP and mailing-list
sig is a quote from Richard Stallman:
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."
Again, thanks for the debate, as it has informed my own thoughts on the
matter, which is after all the purpose thereof, right? I know it'll take
a bit to let it sink in and see how it all settles out, in my own
thoughts.
Duncan
GNU/Linux World Domination for the Wrong Reasons (Datamation)
Posted Mar 13, 2008 7:59 UTC (Thu) by job (subscriber, #670)
[Link]
I believe your analogies are misleading, and sometimes disregard the fundamental differences
between information and hardware. It is sometimes better to try to explain your actual
viewpoint than your analogies.
My counterpoint to your car example is that you are free to modify your car to get any desired
behaviour you want. Of course, if you wanted to use public roads then you need to get an
assurance that it was all done in a safe way, depending on your local laws.
Your counterpoint would be that while I am allowed to do so the blueprints/APIs are not always
publicly available. And less so today than a few years ago especially since digital equipment
in cars are often black boxes (in every way), which is a bit ironic. Then I would say that
while not always available, reverse engineering them is mostly legal and the information is
available from third parties. Which gets us nowhere on the finer points of free software. It
only proves that analogies are like giraffes.