Not really, if absent means “no change”, present means “update” and null means “delete” the three values are perfectly well defined.

For what it’s worth, Amazon and Microsoft do it like this in their IoT offerings.

Rust has perfectly fine tools to deal with such issues, namely enums. Of course that cascades through every bit of related code and is a major pain.

A fuel cell does not mean it’s an ICE. It will still use an electric motor and probably even a small battery.

Hydrogen ICE exist, but are more complex and less efficient.

You could use Hydrogen to produce so-called e-fuels (we had a huge debate about them in Germany), but those can typically be used in normal ICE vehicels.

In the bottom picture it looks like the top “port” is just an air intake.

I mean, other file sync apps upload everything to a third party while you’re working with the device.
Then, when you use another device the first one can be turned off.

Most x86 EFIs are, so the comparison is not really fair.

That’s Canonical building Mir 2.

There also isn’t a loop instruction though.

Not here, because it’s being used as a function argument.

It’s not even controllable RGB? Just shitty rainbow all the time?

The truth is that there is value in both a generalist and a specialist.

I think that’s fairly obvious with the smaller text and context.

Also a neverending discussion around some “newer” words or brands such as Ketchup, Nutella, etc.

There is a wrapper for podman supporting compose.

But maybe it’s time to use kubernetes deployments or pods instead of compose files…

Wow, I was sure Raspberry Pi were pretty good about mainline support, especially since multiple distros support the platform.
Software support is still very good compared to pretty much every other arm board.