this post was submitted on 05 Mar 2024
996 points (97.2% liked)
Memes
45655 readers
1692 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Open source projects do not grow by themselves. It requires serious effort from dedicated developers to develop and maintain applications as complicated as an emulator. Yuzu's developers are banned from doing so and I don't see how this incident could help bringing more developers.
I'm sure there will be developers capable enough to keep it working on new operating systems. Games that worked with it until now will keep on working, and that's what matters to most people anyways. No need for major changes to the codebase.
I truly admire the optimism but I think it's also important to understand the hard work and dedication that the Yuzu developers put in.
You're correct that someone probably will fork it and development will continue but it is not simple and it requires a very specialized skill set.
I just think it's important to never take for granted the people who take time out of their lives to give the community something so wonderful.
I don't think it's diminishing the work of the Yuzu devs, but more so a strong belief in the capabilities of the open source community. They worked their asses off and are extremely talented, and I'm sure there are others who will hop in and carry the torch.
I'm also curious if there's a programmatic way to circumvent the argument Nintendo made about bypassing DMCA by separating the emulator from the code that utilizes the keys such that you can use tool A to bypass DMCA, and tool B (Yuzu with game decryption removed) to run the circumvented game. In this case tool A already exists, and tool B could be a fork of Yuzu.
This is similar to how Tachiyomi forks can still exist. Even though tachiyomi never had a real case go to court, they've separated the extensions library from the reader so nothing comes "preloaded" with any potential copywrite infringing parts.
That's really easier said than done
Yeah, of all the forks and mirrors I've checked out, none of them even have the Android builds. Obviously I've not checked them all, but still...