In an emulator you're capable of running a piece of software in a hardware that it wasn't designed to be run. In Wine you still need a hardware originally designed for the game (x86 CPU, graphics card, etc) because it only fakes that it is being executed under Windows by providing Windows APIs, but the underlying hardware must still be compatible.
Flatpaks are easier to use in most distros. If you're using NixOS, then Nix of course. But if you want to do a lot of CLI stuff, then Nix may be better too.
In Spain, I think only ING has this cashback procedure that allows you to withdraw cash from supermarkets, but it's only for its own clients. It's not very popular and I have to admit, that as an ING client, I've never use that feature. More traditional banks still have lots of ATMs and banks like ING cover the ATM fees if you withdraw enough money (if you withdraw 200€ in one go, it's free for example).
I agree that Alpine Linux shouldn't be recommended to newbies but I don't like the explanation. Distros like Alpine Linux are good for the whole Linux ecosystem, as they avoid monoculture and bring diversity to the software, which in turn they foster competition. Like a biological ecosystem, betting everything into one particular specie is a recipe for disaster. Some examples: Glibc has found many bugs because musl did things differently, and it turned out that glibc was not following the standard (also musl had bugs on its own), GCC was stuck until Clang came out and developers started to prefer Clang,...
VLC ships their own codecs which is great on Windows, but a bit suboptimal on a typical Linux desktop installation since you're probably going to have GStreamer or ffmpeg available too for the rest of the software like video editors, web browsers, etc
IPv6. Lack of IPv4 addresses it's a problem, specially in poorer countries. But still lots of servers and ISPs don't support it natively. And what is worse. Lots of sysadmins don't want to learn it.
Supercomputers are usually just a lot of smaller computers that happen to be connected with very efficient networking. Then you use something like MPI to simulate a big pool of shared memory.
In an emulator you're capable of running a piece of software in a hardware that it wasn't designed to be run. In Wine you still need a hardware originally designed for the game (x86 CPU, graphics card, etc) because it only fakes that it is being executed under Windows by providing Windows APIs, but the underlying hardware must still be compatible.