zlib-ng VS dolphin

Please note that allowing for 2% bigger resulting file could mean huge speedup in these circumstances even with the same compression routines, seeing these benchmarks of zlib and zlib-ng for different compression levels:

https://github.com/zlib-ng/zlib-ng/discussions/871

IMO the fair comparison of the real speed improvement brought by a new program is only between the almost identical resulting compressed sizes.

It is much faster than miniz_oxide and all other safe-Rust implementations, and consistently beats even Zlib. The performance is roughly on par with zlib-ng - sometimes faster, sometimes slower. It is not (yet) as fast as the original libdeflate in C.

Zlib-ng doesn't contain the same code, but it appears that their equivalent inflate() when used with their inflateGetHeader() implementation was affected by a similar problem: https://github.com/zlib-ng/zlib-ng/pull/1328

Also similarly, most client code will be unaffected because `state->head` will be NULL, because they (most client code) won't have used inflateGetHeader() at all.

I wonder if zlib-ng would make a difference, since it has a lot of optimizations for modern hardware.

https://github.com/zlib-ng/zlib-ng/discussions/871

zlib-ng also has adler32 implementations optimized for various architectures: https://github.com/zlib-ng/zlib-ng

Might be interesting to benchmark their implementation too to see how it compares.

zlib-ng: https://github.com/zlib-ng/zlib-ng/blob/develop/functable.c

(2) There are many packages that rely upon zlib and minizip and switching those underlying dependencies is easier said than done. We can't drop zlib completely and switch: "The idea of zlib-ng is not to replace zlib, but to co-exist as a drop-in replacement with a lower threshold for code change." - https://github.com/zlib-ng/zlib-ng

There are already active zlib forks (e.g. https://github.com/zlib-ng/zlib-ng), the problem is with having people move to them. It takes a lot of effort to move mindshare from the original version to a fork, there's some historical examples of it happening, but not a ton.

Dolphin ships with a bunch of keys in the source code[0]. So do almost every other emulators for any console from 6/7th gen consoles (ps3, xbox360, gamecube), see delroth's post on the matter here[1]. It's really not that simple - jurisdiction matters a lot, and also Nintendo's own priorities.

[0]: https://github.com/dolphin-emu/dolphin/blob/34527cadcce49a9a...

[1]: https://delroth.net/posts/emulation-crypto-keys-copyright-dm...

GameCube/Wii: Dolphin is the best GameCube/Wii emulator in my opinion: Download Dolphin

Dolphin has actually had this for their macOS builds for over a year now.

https://github.com/dolphin-emu/dolphin

Dolphin (GameCube/Wii) Emulator: https://dolphin-emu.org/

Though these consoles did not support stereoscopy originally, the Dolphin emulator can add it and output SBS. My experience was a bit mixed. Your mileage may vary.

You install Dolphin emulator, go into settings and make a folder for your games where it says "directory", and then you just stick your game in the folder. That's pretty much all there is to it, that's why I think Dolphin is the best emulator.

Dolphin

Platform: Gamecube. The remaster scrapped the local co-op entirely (booo). This one is a bit tricky but works perfectly once setup properly in Dolphin.