• 27 Posts
  • 122 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle




  • It’s like regular Fedora KDE, except that it avoids this problem of traces of past experiments everywhere.

    Kinoite is much more than that: it is an atomic and immutable spin of Fedora KDE. This has big implications but the gist of it is that:

    1. You can roll back to any previous version if anything breaks

    2. The base system cannot be modified

    3. If you need to install RPM packages, you do that by adding “layers” on top of the base system, and these can be removed if needed to go back to a clean base system

    4. You can switch from one spin to another by “rebasing”, but it is recommended that you remove any additional layer first and that you stick to the same desktop environment







  • Android has always been developed in a closed-source manner by Google engineers, the recent changes only reduces the visibility of ongoing changes and the ability for developers outside of OEMs to contribute to Android (such contributions were already rare).

    This is explained further in this article:

    While some OS components, such as Android’s Bluetooth stack, are developed publicly in the AOSP branch, most components, including the core Android OS framework, are developed privately within Google’s internal branch. Google confirmed to Android Authority that it will soon shift all Android OS development to its internal branch, a change intended to streamline its development process.








  • Most likely they use a translation layer (think Wine, Proton or DXVK) rather than emulation, since the Switch 2 hardware is not completely different from Switch 1 and it’s not as costly as emulation, so I would say neither.

    Edit to clarify emulation vs translation layer:

    Emulation re-creates the entire hardware, while translation layer translates programming instructions intended for one platform to another, just like you would translate “one plus two” from English into “um mais dois” in Portuguese for exemple.

    Since both Switch don’t have completely different hardware (unlike PS3 and PS4 for example) it’s probably easier and much more efficient to simply translate instructions that were specific to Switch 1 into Switch 2 instructions.

    Edit 2: also Yuzu and Ryujinx are designed to emulate Switch on the x86 architecture, and since Switch 2 (and Switch 1) run on ARM, I’m pretty sure these emulators wouldn’t run on Switch 2 without massive re-engineering efforts. Also, as someone else said, these projects are reverse-engineered, it makes much more sense that Nintendo engineers create an emulator from scratch using their own internal documentation of Switch 1 architecture (again, it’s unlikely they went for emulation as I stated above) so the result is much more reliable than both Yuzu and Ryujinx.