This sounds like some silly bug in libinput.

There’s nothing in wayland that would care about whether a mouse was connected wirelessly, but libinput may not be detecting it properly when wired. I’d try reporting it, the fix is likely to be trivial.

No, it’s a dev build and a real wii doesn’t have enough memory to run it.

It’d work on a dev kit, if you had one.

Feel free to say it any way you like, it makes no difference:

• 1.58 meters
• 158 centimeters
• 1 meter 58 centimeters

It’s all the exact same thing, nobody will bat an eye.

Regardless of what the website says, waydroid isn’t an emulator by any meaningful definition.

It’s a container that runs on top of your regular linux kernel (with some very cool desktop integration features), java/kotlin applications run as natively as they’d run on your phone.

I felt the same way about webp when it came out.

In practice it doesn’t really matter:

• if you’re encoding the file you know how you’re doing it.
• if you’re receiving the file, you get the pixels you get no matter how it was encoded.
• if you’re sending the image through some third party service, they’re going to reencode and mangle it anyway so there’s no point in worrying.

Also, it turned out that even if it’s quite good, lossless webp is rarely seen in the wild because svg is more convenient.

Heif is covered by patents in the mpegla patent pool of which apple is a member. They have a vested interest in it becoming mainstream.

It would depend on whether you think elop was a Microsoft mole al along 😉.

By the time of the Microsoft acquisition, focus had already shifted to Windows phones.

No, the tape is an endless loop, the end is the same as the beginning.