Hacker News new | past | comments | ask | show | jobs | submit login

The problem is that your reasoning only works for those capable of producing their own software.

That is entirely the point. One of the stated aims of the GPL is to ensure that everyone is capable of producing software. The GPL attempts to ensure that your software won't ever be redistributed in a form that takes away the user's capability to build on your code.




You're entirely missing my point - for 99% of the population of this planet, producing software is going to forever remain beyond their reach. You can give them all the freedom to do so that you wish, they are still going to remain incapable of actually doing so. The GPL is not un unmitigated good for the vast majority of users.


You're entirely missing my point - for 99% of the population of this planet, producing software is going to forever remain beyond their reach. You can give them all the freedom to do so that you wish, they are still going to remain incapable of actually doing so.

Why? If you said that, for 99% of the population of this planet, literacy is forever out of reach, you'd be rightly laughed out of the room. The increasing importance and preeminence of software in every system we interact with means that programming is a new form of literacy and numeracy.

Not only can the 99% code, but, increasingly, they must. They must, in order to assert control over the software that increasingly controls them.


I must agree with your main point, which is that the typical user just won't have the expertise nor the energy to dive in and modify the code, making the GPL much less useful for them.

There are two obvious ways to solve the problem: find a way to make developers make more software that is useful to end-users (basically the Apple route).

Or, find a solution so that end users themselves can modify their systems. That second route is currently close because of the ridiculous size of current systems. (The volume of a typical GNU/Linux distro is the size of a whole library, and Windows and MacOS are fare marginally better.) The obvious solution there is to reduce the size of our software. http://vpri.org/ is currently attempting to do an OS in 20,000 lines of code (a middle-sized book), and they are doing quite well.

Note that doing the "Let's Remove the Fat" route, if successful, will massively reduce the amount of necessary programming work. Plus, more of that work will be done by the end users themselves. That could have dire consequences if we don't prepare for it. (A similar example would be automatic Google cars driving truckers out of business –no pun intended.)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: