Natanael

Yeah blackbox testing is a whole thing and it's common when you need something to follow a spec and be compatible

If it's illegally parked and you're not the property owner you definitely don't have to pay to get it towed

What distro do you use which thinks an archive file needs executable permissions?

Alternatively, what distro / file explorer can't recognize the MIME types for archives (which has nothing to do with permissions but it's the only relevant error that makes sense)?

Let's post this on matrix, then scuttlebutt

Even the name Meta was trademarked by others and they paid a lot for the rights to use it

Fee speech

Auto insertion of space in mobile keyboards. Usually they also remove the preceding space when you press enter, but if somebody manually presses space after an automatic insertion of space then you get double spaces and only one will be removed

Google's keyboard is the absolute worst for that, tried using it for a bit but I'm back to SwiftKey which isn't absolutely insane (and which has more customization options too)

I still miss Swype too, and hopefully one of the open source keyboard apps will get good enough to replace all of them soon enough

Yes and no, it's not about the instruction set size but about general overhead.

The x86 architecture makes a lot of assumptions that require a bunch of circuitry to be powered on continously unless you spend a ton if effort on power management and making sure anything not currently needed can go into idle - for mobile CPUs there's a lot of talk about "race to idle" as a way to minimize power consumption for this exact reason, you try to run everything in batches and then cut power.

The more you try to make ARM cover the same usecases and emulate x86 the more overhead you add, but you can keep all that extra stuff powered off when not in use. So you wouldn't increase baseline power usage much, but once you turn everything on at once then efficiency ends up being very similar.

There's already CPUs with extra instructions specifically designed for efficient emulation of other instruction sets. This includes ARM CPUs with x86 emulation at near native speed.

And if it won't be ARM, it might be RISC-V

And yet it happens, just look at the molasses that is Teams