I really liked the part on expectation of reciprocation that GPL enforces. The more I think about it, the more I favor a stance like that.
Exactly. The GPL is a self-enforcing improvement cycle, vs the MIT which lets anyone just take the code, and offer nothing back.
I do get the whole “which is freer” argument, and it really boils down to whose freedoms are you caring more about? Developer freedom, or user freedom.
The GPL (And AGPL) target user freedoms, MIT/BSD target developer’s freedoms. Sadly, though “developers” tend to be corporations now, not individual contributors.
All these people clamouring for a new graphical gopher client are tempting me to make an electron monstrosity.
You were so preoccupied with whether or not you could, you didn’t stop to think if you should.
90% there: https://www.npmjs.com/package/copher
Sadly, people will find it suspect, since DARPA did it, like with TOR. Baselessly.
People will find a way to complain about everything. The description sounds great, though. Open-source is cool. I’m curious what it’ll be coded in (crossing fingers for Ada).
i’d be interested in serving this at gopher://tilde.news. thoughts? what would i need to do?
Oh that would be excellent!
I was pretty disappointed by this. First, it’s a blatant ad for the license that this lawyer worked on, but also it shows a shocking lack of familiarity with MIT and BSD licenses, where they’ve been used in practice, where they’ve been reviewed in the courts, and exactly what things mean. In my opinion this piece crossed an ethical line. I’ll be aggressively avoiding Blue Oak as a result.
I totally agree with you and @aewens that this is propaganda for Blue Oak.
However the author knows his stuff on MIT and BSD quite well.
As for Blue Oak, the only thing I like about it is its language.
It’s a permissive license designed to remove ANY burden on corporations that want to exploit the free labor of the open source developers.
It’s not designed to maximize the CREATION of Commons, but their exploitation and privatization. So I agree that avoiding Blue Oak is a good idea if it doesn’t align with your interests and values.
This is really important stuff. Even my tools which do respect proper config directories are doing it lazily, looking in ~/.config and such instead of checking the XDG environment variables first. I’ll have to pull this through.
Yeah, after reading this article I decided to make an effort to always utilize the XDG environment variables for anything software I write needing to store data for a user. Would definitely make for a better experience using Linux as a platform.