Solution Found for Yuzu/SDK issues, someone has already rewritten alot of Yuzu #188

Open
opened 2024-06-10 16:34:18 +02:00 by chaphidoesstuff · 3 comments
Collaborator

Is there an existing issue for this?

  • I have searched the existing issues

What feature are you suggesting?

for the plan to purge yuzu/sdk code from suyu, the plan was being worked on very little, but with the discovery of a WIP emulator that appears to be yuzu but completely rewritten, called Nozomi
https://github.com/noumidev/Nozomi/tree/main

Why would this feature be useful?

it was part of the post fallout plan to rewrite alot of suyu to distance it from yuzu and the sdk allegations

### Is there an existing issue for this? - [x] I have searched the existing issues ### What feature are you suggesting? for the plan to purge yuzu/sdk code from suyu, the plan was being worked on very little, but with the discovery of a WIP emulator that appears to be yuzu but completely rewritten, called [Nozomi]([https://github.com/noumidev/Nozomi/tree/main]) https://github.com/noumidev/Nozomi/tree/main ### Why would this feature be useful? it was part of the post fallout plan to rewrite alot of suyu to distance it from yuzu and the sdk allegations

I'm still yet to see anyone actually confirm specifically which parts of the code are from the Nintendo SDK.

I'm still yet to see anyone actually confirm specifically which parts of the code are from the Nintendo SDK.
Author
Collaborator

I'm still yet to see anyone actually confirm specifically which parts of the code are from the Nintendo SDK.

skoz says loader.h and torzu dev says all the stuff specifically for the actual switch os

> I'm still yet to see anyone actually confirm specifically which parts of the code are from the Nintendo SDK. skoz says loader.h and torzu dev says all the stuff specifically for the actual switch os

The now deleted ghost account in the other issue already clarified the two enums and other placeholder variables in loader.h are similiar/the same as ryujinx. What specifically has the torzu dev changed or pointed out comes from the switch sdk and why? I checked their git and saw nothing and no clarification, deleting the offending code would have sufficed for cleaning the project up if that were the case.

Furthermore; even if the code did match switch sdk definitions it does not mean that the dev that implemented said code copied or ever looked at the switch sdk. Perfect example of this is the ReactOS project. They have headers that probably match or are similiar to the semi-public windows xp source code headers but they and I have never looked at said headers. Just because its implemented the same doesn't mean they infringed on nintindo's code with clean room reverse engineering. The company representing the yuzu devs settled out of court so there's no way for us to know if the yuzu devs looked at the switch sdk and then contributed code ever. Obviously if nintindo could have proven that the code was copied then they would have continued their court battle so they could always take down this code wherever it goes. The fact is it was a political like manuver to keep the switch profitable since this emulator popped up and worked on android devices for the massess far before the switch EoL. There have been other emulators that developed too fast in the past this has happened to, this is nothing new. The code lives on since it was libre.

The now deleted ghost account in the other issue already clarified the two enums and other placeholder variables in loader.h are similiar/the same as ryujinx. What specifically has the torzu dev changed or pointed out comes from the switch sdk and why? I checked their git and saw nothing and no clarification, deleting the offending code would have sufficed for cleaning the project up if that were the case. Furthermore; even if the code did match switch sdk definitions it does not mean that the dev that implemented said code copied or ever looked at the switch sdk. Perfect example of this is the ReactOS project. They have headers that probably match or are similiar to the semi-public windows xp source code headers but they and I have never looked at said headers. Just because its implemented the same doesn't mean they infringed on nintindo's code with clean room reverse engineering. The company representing the yuzu devs settled out of court so there's no way for us to know if the yuzu devs looked at the switch sdk and then contributed code ever. Obviously if nintindo could have proven that the code was copied then they would have continued their court battle so they could always take down this code wherever it goes. The fact is it was a political like manuver to keep the switch profitable since this emulator popped up and worked on android devices for the massess far before the switch EoL. There have been other emulators that developed too fast in the past this has happened to, this is nothing new. The code lives on since it was libre.
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: suyu/suyu#188
No description provided.