Negative Voices Regarding ShiroSU​

Disclaimer​

We do not compete with otherROOT implementations, and we are not interested in interpersonal conflicts. So no matter what others say, we hope you won't mind, and just choose what you want, use what you think is useful.

SUUandSSUare sister projects, please distinguish them.SUUis namedSuYu, and SSU is an abbreviation ofShiroSU. Hereafter referred to asSSU.

Too Many Negative Voices Since SSU Project's Inception​

• Suspicions that SSU is a Fork of KernelSU.
• Another KernelSU branch; no comment.
• SSU is a PPT project.
• Hype before the code is even complete.
• If SSU's SU could be written, I wouldn't say anything about it.
• Looks like an empty shell, just using KernelSU's API.

And a series of negative comments. Furthermore, any detailed criticism of a project in thePreviewstage is meaningless.

Open Source Statement for SSU Project​

TheSSUproject is a subsidiary ofOOM. WG.. @AnYinSaiTing is the developer for the user space implementation, and @Linso is the developer for the kernel space implementation. The SSU documentation was written by @YumeYuka and optimized collaboratively with other members. As of the end of June, theSSUmanager has been developed to be usable as amodule manager. The kernel space implementation's progress is slow due to @Linso's personal reasons.

SSUhas opened source code for someconfigurationsandcore components, seehttps://github.com/OOM-WG. The manager's entire code was written by @AnYinSaiTing, and @YumeYuka participated in optimizing a small part of the page. The user space code has completely avoided theGPLprotocol, including theWebUIimplementation. The kernel space code was completed by @Linso, and the openness degree is determined by the completeness of @Linso's work. For the documentation part, the documentation usesvitepress, and currently only considers opening the article part.

For specific open-source directions, theSSUproject will mainly open-source more mature frameworks/tools developed during the development process, and opening the core source code is not the primary goal.

TheSSUinterface is developed using third-party libraries. Due to the lack of third-party libraries and issues in some UI bottom layers, SSU's developers are currently unable to resolve them.

Regarding SSU == KernelSU Fork​

Evaluation: Playing withKernelSU Next.

The members ofOOM. WG.explicitly stated in posts that it is not aKernelSUbranch. Jumping to conclusions is premature.SSUis still under development, and the root implementation needs to wait for the kernel space implementation code's development progress.

AlthoughSSUis also a kernel-based root implementation, this does not imply a direct connection between the projects. Overlapping in certain technical implementations is a normal phenomenon, but over-interpreting this overlap is meaningless.

Some people say it's aKernelSUAPI shell, butKernelSUdoes not have any universal APIs. All ofSSU's code is for general development targeting various module-based root implementations. Furthermore,SSUis primarily aKotlinproject, and most of the code is implemented usingKotlin'sJVM/Native. Only a small portion of the code, whichKotlincannot implement, is implemented inC++. While other root implementations mostly useKotlin/Javafor application development andC++/Rustfor user space tools, claimingSSUis aForkis purely unfounded.

Moreover, if you followSSU's historical updates and delve into the specific update content, you will find thatSSUgradually implementedSU CLI, general operations, and general module installations. These are merely preparatory steps for subsequent features, and they are not included in the update logs.

Conclusion​

We will ignore negative voices.SSUwill be a highly independent implementation, not a pie in the sky. It is expected to achieve kernel space implementation before the end ofJuly. Stay tuned.

Contributors

白彩恋 YumeYuka

Changelog