Spaces in file names will always be fiddly though. It'll work, but it'll still be wrong, because arguments are space separated, and having spaced file names totally messes with that.

Good point. Do filesystems use a normal form to at least prevent having two files with effectively the same name?

I should point out the flip side though, that there's no avoiding Unicode in filenames. Users in languages that don't use the Latin alphabet (such as Japanese, Chinese, Korean, Hebrew, Arabic, Greek and Russian, and the list could go on) can reasonably expect to be able to give a file a name they can read and understand with no extra effort. All the software woes that come with it - too bad, software needs to deal with it.

You don't necessarily need speech for consent since non-verbal/mute people exist.

It can't say no either /s

I feel like unicode in the filename is heavily against the spirit of using squashfs, or at least the ways I've seen it used.

Well, a.out doesn't make much sense these days.

Gotta move to .elf

Pi Pico SDK does. Well, the version for debugging symbols, anyway. Regular executable is .uf2.

I reserve .elf for executables for other platforms, like microcontroller firmware.

wii homebrew developer maybe?

You are actually correct. They can contain archived files or resources that can be unpacked with an archive program (including on Linux btw), but they aren't just a zip file. That's why my Linux archive manager (ark I think) offer to open one, but won't execute it. They can see the extra content even if they can't execute the file as intended.

Aren’t the x-suffixed files just an xml format?

By "zip file", I meant a compressed archive. I'm not as nerdy as you guys are so I see now that there is a difference. I appreciate the correction.

That said, you have to admit that it's still cool that these different file formats are nothing more than archives. Maybe not to you but it blew my mind when I first learned this.