Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'd argue that he quite clearly does actually make that distinction, though perhaps with different words. (I'm also under the impression that he elaborates quite a bit on the core concept, though I'm unable to easily find a reference). But, e.g. from the GNU Manifesto, 1985:

> GNU is not in the public domain. Everyone will be permitted to modify and redistribute GNU, but no distributor will be allowed to restrict its further redistribution.

The phrasing is a bit different (it's from a point of view of freedom of distribution), but essentially he's pointing out the copyleft idea; that the code can never go back to a model that doesn't provide the same guarantees.

So, there's the freedom of distribution, versus the freedom of someone to restrict the distribution. Both cannot exist at the same time. He's quite clear that the benefits of freedom of distribution outweigh (any potential) benefits of restriction, so he's happy to deny others that "freedom". It gets phrased in many ways, but right or wrong, that's what it is. In that sense, I agree with the poster I responded to; to the person doing the coding themselves, an MIT license leaves more doors open, and hence feels more free.



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

Search: