137
Ladybird Browser Team Selects Swift as Preferred Language
(linuxiac.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Aug 2024
137 points (90.1% liked)
Open Source
31736 readers
131 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
I've read through your links. They don't have much to do with the codebase itself, but with protecting the trademarks.
From what I read, you're free to change whatever you want. You just can't go around using their trademarked names for your modified version.
Please read this and try again.
https://www.gnu.org/philosophy/free-sw.en.html#packaging
Yeah, I don't exactly think it's particularly burdensome to have to rename your fork so that people don't confuse it with the software you forked from. Without this restriction, FOSS projects would have absolutely zero recourse against bad actors. A non-FOSS competitor could just waltz in, fork their code and turn it into absolute hot garbage, convincing enough people that it's the original project to make it all worth their while.
Dude, if you're being obtuse on purpose because you have an ax to grind against Rust, try a different approach. You're not getting anywhere, clearly by the fact that no one agrees with you.
If you don't like that Rust has a restricted trademark, then call that out instead of trying to label the software and it's license as non-free. It's literally called out in my source that name restrictions ipso facto does not violate freedom 3.
But if you genuinely believe that the implementation of the Rust language and it's trademark is burdensome to create a fork, and you want people to believe you, then you gotta bring receipts. Remember, the benchmark that we both quoted is that it "effectively hampers you from releasing your changes". It being "not a piece of cake" doesn't cut it.
Hint: Google Rust forks since their existence also undermines your claim.
Good luck.
As an outsider with no skin in anyone's game, I find it a bit disingenuous to say that one person's interpretation of subjective terms is somehow less "correct" than anyone else's.
That... is not a restriction on freedom 3. You could complain about your inability to use the rust name for anything you want but that is not the same thing as your ability to distribute modified versions of the software. It is also fairly standard practice for foss software to restrict the use of such trademarks. For example, Gnome does pretty much the same thin. FreeBSD as well. Libre Office also has similar restrictions, although they are defined more nebulously. It is not clear to me what usages are allowed with the Linux trademark but they certainly do restrict who can use it and for what and you must get permission before using it. See also, about trademarks in FOSS: https://www.lexology.com/library/detail.aspx?g=9d96e1bf-bced-48f7-b5b4-ee561e7a9348
The software is free. The trademarks are not. The four freedoms are about the software and not about trademarks. You could fork Rust and call it Corrosion, just like people have forked Firefox and called it Waterfox.
Its also terrible when it comes to security, specifically crates
There's a reason why software is being made with Rust now. It has the speed of C++ (sometimes faster), has a nice syntax, is memory safe by default, has the best compiler error messages and also the book is very good. I learnt entirely by the book and it's very good at explaining things.