this post was submitted on 25 Jan 2024
341 points (99.1% liked)
Technology
59533 readers
3106 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- 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, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is why copyleft licenses like gpl, agpl, ~~mit~~, creative commons exist. If they use those projects then the derivatives would also need to be open source.
Edit: mit is not copyleft
MIT is free for commercial use and just requires attribution, you aren't required to open source software derived from MIT licensed code.
GPL is also free for commercial use... all open source licenses are. The rendering engines used by Safari (and Chrome/Edge) are GPL.
GPL can be used for commercial purposes, but it requires all software derived from it to also be open source and GPL compatible. So no one whose commercial business relies on selling software will use GPL because their customers can copy and distribute the code.
Neither Safari nor Chrome’s rendering engine is GPL. Safari’s engine is LGPL, which means the binary library can be linked into a closed source program, but modifications to the library’s code must remain open.
Chromium is BSD, which doesn’t even require modifications to remain open. So I can take chromium’s source, change it however I want for my own browser, and never distribute that code.
If Safari’s and Chrome’s engines were GPL, Safari and Chrome would be forced to be open source, and they very much are not.
The thing is that source code is just a small part of an application. For example, Quake games are open sourced, but their assets like textures, models and music are not. Thus you can't just compile the game and call it a day. Another example is all kinds of certificates, they are never part of the source. You can compile the app, but it won't work.
Source code, GPL or otherwise, doesn't matter.
Thanks for pointing it out. I was making a project that uses this license and derivatives had to use MIT license. I forgot that it's not copyleft and so it allows derivatives to be proprietary.
Correct. This is also why Apple switched to zsh as the default shell over bash. They still ship Bash 3.2 in macOS, because from 4.0 on, Bash started using GPLv3 instead of GPLv2.
I'm not against the idea of creating proprietary software out of open-source software, if the license allows that. However, I am always against this practice of "closing the door behind you".
I agree. If they use open source code. They should give back. It doesn't matter if it was copyleft or permissive.