Figured I'd do the math on the power required.

In the article, they show a iPhone 15 Pro, which has a 3274 mAh battery, so let's go with that. Assuming a 3.7 V battery and a 1 minute charging time, that's 3274 mAh × 3.7 V / 1 min ≈ 727 W.

It's not just about quality (AAC is perfectly fine quality-wise), it's IMHO more about the extreme latency, and the fact that they have to to drop down to terrible-sounding HSP/HSP when using the microphone, since A2DP is monodirectional. Sucks that they don't support LE Audio.

Why do you feel the need to install an app for a coffee shop?

Another alternative then would be Restic. That's what I'm using for backups

And the conditions are still better than what the collective agreements would require?

That one was always available though

That said, many of our clients still don’t support utf-8 so its all ascii and non-latin alphabets are screwed.

Ah, yes, I heard about that sort of thing. Some bank getting a GDPR complaint because they couldn't correct the spelling of someone's name, because their system uses EBCDIC.

I assume you're gonna back that up with a double blind ABX test?

How about Qt

I find it ridiculous to have a car tied to a specific mobile OS

Android devices sold in the EU display a warning when headphones are connected and the user tries to raise the output volume level above 85 dB

No the don't, they pop that up when you try to raise the volume above some arbitrary percentage. What volume that corresponds to depends on the audio hardware, it might be barely audible. And now they're apparently gonna make that crap even worse.

Rust does. But you get:

error: unknown start of token: \u{37e}
 --> test.rs:2:30
  |
2 |     println!("Hello, World!");
  |                              ^
  |
help: Unicode character ';' (Greek Question Mark) looks like ';' (Semicolon), but it is not
  |
2 |     println!("Hello, World!");