this post was submitted on 13 Apr 2025
645 points (96.5% liked)
Technology
68772 readers
4446 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's what I said.
I'm saying it is necessary to achieve the aims of the GPL.
If it was just about ensuring the source is free, the MIT license would be sufficient. The GPL goes further and forces modifications to also be free, which relies on copyright.
Which would make GPL toothless, but that’s fine because it would no longer be necessary.
Until copyright no longer exists and everything is in the public domain, as I said.
How are you going to enforce the GPL in a world where copyright doesn't exist?
And that's what I'm saying, you can't, therefore the aims of the GPL cannot be achieved. The GPL was created specifically to force modifications to be shared. The MIT license was created to be as close to public domain as possible, but within a copyright context (the only obligation is to retain the license text on source distributions).
If everything is public domain, then there would be no functional changes to MIT-licensed code, whereas GPL-licensed code would become a free-for-all with companies no longer being obligated to share their changes.