>Each program on the Wii is basically its own Operating System. So you’re switching between Operating Systems when changing between/opening programs.

// WAT

>As Alex Rossie said legacy consoles, arcades, etc… reset memory and cpu regularly, it’s a form of garbage collection. What dlcarrier is eluding to is Wii has several little Operating Systems they call IOSes. While using the Wii, navigating menus, launching games, updating the system, the Wii is rebooted into one of many different Operating Systems.

>Every game or menu applet could have its own IOS version.

>IOS is versioned in a somewhat unique way. Instead of there being a single canonical version of IOS, there are multiple branches, each typically corresponding to one or more versions of the Wii SDK. Each branch is apparently specified to have a completely frozen API, and old versions are only updated to patch bugs (often security bugs) - Nintendo at one point created an entirely new IOS branch that differed only in the default value for the TCP buffer size. A fully updated Wii contains one copy of the latest version of each branch of IOS. On a Wii, these are installed as separate noscripts, often called "IOS slots". Due to this design, it is generally considered safe to uninstall, reinstall, or patch an IOS or IOS module, as long as it is not the slot used by the System Menu - if anything goes wrong, the broken version can be safely uninstalled and a vanilla copy reinstalled.

И еще пачка феерических костылей)
https://youtu.be/ymUnMArNu1g?t=82
https://youtu.be/ymUnMArNu1g?t=342
https://youtu.be/ymUnMArNu1g?t=522

продолжение истории)

Блять, наконец-то кто-то сделал ЭТО

@silero_voice_bot