4 ms·
That may all be true, but we used to get by on the most basic and plain English of agreements and a healthy dose of common sense, all of which is just as valid
by Silhouette 15y ago
That may all be true, but we used to get by on the most basic and plain English of agreements and a healthy dose of common sense, all of which is just as valid in court.
The world is not a better place because ordinary people with no legal training and better things to do with their time are subject to multi-page formal agreements, which most of them have never actually read, never mind understood. I don't care whether it's a software licence agreement or the terms for a network service, it's still the same basic problem.
- icebraining 15y agowe used to get by on the most basic and plain English of agreements and a healthy dose of common sense, all of which is just as valid in court. Yes, but who's "we"? Did that include the thousands of business that nowadays use and contribute to OSS and also have lawyers to worry about those things? The world is not a better place because ordinary people with no legal training and better things to do with their time are subject to multi-page formal agreements, which most of them have never actually read, never mind understood. But it was copyright that created that, by prohibiting any redistribution and derivation by default. FOSS licenses are a way to counter-act that and give you rights. And while the GPL is not as short as we would like, the reality is that it created a standard; you just have to read it once to know the license of more than 50% of the FOSS projects out there. That seems a time saver, not killer.
- Silhouette 15y agoDid that include the thousands of business that nowadays use and contribute to OSS and also have lawyers to worry about those things? You know it didn't. But I don't really see how that's relevant to my point. If it takes several pages of legalese to define what "freedom" you are giving someone, you might want to consider whether you're using the right word for what you're doing. But it was copyright that created that, by prohibiting any redistribution and derivation by default. No, it wasn't. It was bad lawyers who can't write plain English, and picky people at the FSF who tried to fine-tune everything instead of stating a clear guiding principle. There are plenty of other licences that are very much shorter. And while the GPL is not as short as we would like, the reality is that it created a standard; you just have to read it once to know the license of more than 50% of the FOSS projects out there. That seems a time saver, not killer. Sorry, but that's just wishful thinking. Firstly, I suspect that a lot of people use the GPL not because they like or understand it but because it was the peer pressure "what you do" option for a while. Those kids used to just give their code away as freeware and no-one was any worse off for it. Secondly, it's not really a standard when there are at least three styles of GPL licence that come up reasonably often in discussions (GPL, LGPL, AGPL) and then there's the whole v2/v3 mess as well. In fact, this kind of fragmentation is probably a large part of why we're having this whole discussion on HN today. Finally, while I respect the goal of trying to have some standardised licensing, the only standard I've observed in practice is that, unless you're working in an organsation where everyone values GPL-style licensing and uses it as an integral part of your business model, the lawyers and managers are likely to blanket ban any use of GPL'd code because the risk of the viral contamination effect is too high to justify any benefit from using it. On the other hand, it's easy and feels safe to reuse code that comes with a no-nonsense BSD/MIT style licence that says in plain English that you can use the code without understanding several pages of legalese with subtle implications. That saves time.
- icebraining 15y agoNo, it wasn't. It was bad lawyers who can't write plain English, and picky people at the FSF who tried to fine-tune everything instead of stating a clear guiding principle. There are plenty of other licences that are very much shorter. Well, unlike permissive licenses, the GPL is an hack on the copyright system; they probably wanted to make sure it would hold up in court. But the GPL isn't really that long; the 2.0 is only 340 lines of 80 characters. Yeah, it's long compared to MIT, but it's still a fraction of most legal documents. Firstly, I suspect that a lot of people use the GPL not because they like or understand it but because it was the peer pressure "what you do" option for a while. Those kids used to just give their code away as freeware and no-one was any worse off for it. "Freeware" doesn't include the right to modify and re-distribute. Yes, we were certainly worse off for it. If you mean Freeware as a different concept, well, then it's easy to see why licenses are useful - they clearly define that stuff, so you can sleep at night knowing your business or webapp or whatever won't get sued to the ground tomorrow. Secondly, it's not really a standard when there are at least three styles of GPL licence that come up reasonably often in discussions (GPL, LGPL, AGPL) and then there's the whole v2/v3 mess as well. The differences between the three versions are minimal - a clause or two more, nothing else. The v2 vs v3 issue is problematic, I agree. On the other hand, protection against software patents is important. MIT, for example, provides none. It seems irrelevant 'till you get hit by a patent troll, like startups are already getting hit. Finally, while I respect the goal of trying to have some standardised licensing, the only standard I've observed in practice is that, unless you're working in an organsation where everyone values GPL-style licensing and uses it as an integral part of your business model, the lawyers and managers are likely to blanket ban any use of GPL'd code because the risk of the viral contamination effect is too high to justify any benefit from using it. True. But unlicensed or implied licensing is dangerous too - you need some kind of legalese. On the other hand, it's easy and feels safe to reuse code that comes with a no-nonsense BSD/MIT style licence that says in plain English that you can use the code without understanding several pages of legalese with subtle implications. That saves time. Wait till you base your company on someone else's MIT licensed code and then get hit by a patent lawsuit from them or a troll with their patents. Safe? I don't think so.
- Silhouette 15y ago