![](/static/0b35d4a1/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
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.
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.
In the bottom picture it looks like the top “port” is just an air intake.
The option to use TOTP is already well hidden. It’s not like someone who does not know what he is looking for and uses an Authenticator already will accidentally select it.
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.
Free is a loaded word and in FOSS it means “free as in freedom” as opposed to “free as in free beer”.
That’s not even free, and more importantly not free and open source.
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.