3 ms·
You've taken that quote out of context, as the next sentence dispels your fear of having to help your mother debug her cell phone. But, to answer that particula
by SwellJoe 16y ago
You've taken that quote out of context, as the next sentence dispels your fear of having to help your mother debug her cell phone. But, to answer that particular argument:
It can't help the previous generation in any notable way. That ship has sailed.
But, the next generation can be more capable than the current one, assuming we pass on the tools they need and a culture of learning and sharing discoveries. So, don't bother teaching your mother to code, unless she actually wants to learn. Teach your kids and give them the tools they need (which includes a huge variety of source to learn from).
- EGreg 16y agoI think that in the future, I wouldn't expect everyone's kids to be know enough to provide patches for software they use. Rather, there has to be a responsive community of developers around the product, with a good TOOL (like a bug tracker) which the kids could use to report a bug and anther TOOL to capture the bug in the app and send the extra info. While everyone would have the freedom to contribute patches, most people aren't going to be educated along this line, or know the product very well. It is the tools that we must improve, although the principles of software freedom enforced in the GPL help protect people.
- dwc 16y ago> You've taken that quote out of context, as the next sentence dispels your fear of having to help your mother debug her cell phone. If the next sentence dispels that fear, then the quoted sentence is wrong, and should have been left out altogether. And so it is. This is perhaps the biggest fail of the Free Software movement: co-opting a word, phrase or sentence to fill people with idealistic notions that do not represent what GNU and the FSF are really about. This begins with "Free" which translates into rules and restrictions. If you want truly free, there's public domain or BSD-style licenses. GNU/FSF have goals other than true freedom, and they believe strongly in those goals. Many agree with them. I think everyone would be better served saying what they really stand for, starting with changing the name of the FSF.
- SwellJoe 16y ago"If the next sentence dispels that fear, then the quoted sentence is wrong, and should have been left out altogether. And so it is." Sometimes, a thought or concept requires more than one sentence to express.
- dwc 16y agoYes, but not this time. If that sentence were dropped, the remaining text would be more clear and accurate. That sentence is not true. Why should a user be a developer in an ideal world? Why should one be required to be a developer to utilize software? It's not even a world that anyone really wants to move toward. The whole idea is very developer-centric, and doesn't represent an enlightened user perspective.
- SwellJoe 16y agoThe point of my comment was that I believe everyone should have the freedom to be a developer. Not that they must be a developer. No one, especially me, has suggested that anyone must do anything. We're talking about freedom here; and I'd like it if users had the same freedoms I've enjoyed over the past couple of decades. That includes having source available for a large percentage of the software I used, so I that I could learn from it and modify it. No one forced me to become a developer in order to use Firefox, but I've always had the freedom to look at and modify the Firefox code (and thus I could, at any moment and without warning or asking permission, transition from being a Firefox user to being a Firefox developer). I think "developer" is a pretty fluid concept, in an ideal world. Anyway, as I've mentioned elsewhere, it is the difference between "may" and "must". You believe I am saying "must", when my intention is "may".
- dwc 16y agoAh, there's "freedom" again, considered only from one perspective. What about the freedom of someone to make their own work available as closed source? What about when it's a derived work that adds novel new functionality? The FSF is against the freedom to do this, because it promotes other freedoms they like better. What if my important set of freedoms isn't a perfect fit with theirs? What if some random users' important set isn't a perfect match with either mine or the FSF's? If freedom is really what you're after, picking some things at the expense of others can get tricky very fast. If you really want freedom, perhaps you can give away all the rights, so that the recipient can decide what they want to do? After all, you still have the code and you can keep giving it away. This is the new BSD license, or MIT license, or ISC license. According to any non-skewed definition of "freedom" they are more free. Objectively. But maybe you want kind of free, free in some narrow ways that preserve things important to you by putting restrictions on those who get your code so that they also have to preserve the same things you like. If so then that's fine! I totally support your right as the author to choose an appropriate license. But that's not about freedom. It's about propagating your view of how things should be. There's nothing intrinsically wrong with that, but it's not about freedom.
- brudgers 16y agoDon't misunderstand me, copyleft is a good approach in certain contexts. On the other hand, MSDN is far more informative than source code comments, a half-hearted Wiki and a snide support forum for the non-professional programmer which populates your ideal world.
- SwellJoe 16y ago"On the other hand, MSDN is far more informative than source code comments, a half-hearted Wiki and a snide support forum for the non-professional programmer which populates your ideal world." This is directly at odds with my own experience. Whenever I've had to work on Microsoft platforms, I've been constantly bumping into walls where I simply couldn't get the information I needed to solve my problems. MSDN, or no, I've generally been much more satisfied with the process of developing free software and for free software platforms. Do you find it difficult to find quality documentation for Python, or Perl, or Ruby? How about GCC or LLVM? I haven't. I've found them to be extremely well-documented. And, when in doubt, I can go to the source (or someone else can go to the source to help me). That's not a privilege one has with non-Open Source software. But, as I mentioned in another comment, the biggest difference in our perspective may be that you think I mean "all users must be developers", when in fact, my intention is, "all users may be developers". We are talking about freedom here after all, and not forcing anyone to do anything. I simply want a culture in which anyone who desires to learn how their tools work can do so.
- brudgers 16y ago>"How about GCC or LLVM?" I assume that unlike the inhabitants of your ideal world and myself, you are a professional programmer. Why would I run LLVM or GCC instead of Visual Studio Express Edition or program in C rather than utilize a .NET language given that neither really supports Windows in the first place? For me, free OS's aren't an option. They don't offer the tools I use to practice my profession. To the degree I program, I have access to really good free programming tools on the Microsoft stack and better integration with my existing tools. And to the degree which I desire to learn those programming tools, being partial to physical books I enjoy the benefits of Microsoft press which simply don't exist in the copyleft world. Again, that's not to say that copyleft doesn't have benefits, but even the best tools are full of dependencies such as the requirement to install Perl to install the Eclipse editor...again something I don't want to have to explain to my father.