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.
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?
Other way round: prefixes that contain “bi” are binary, so 1024-based.
That’s wrong, data is still usually encrypted.
A locked bootloader ‘just’ prevents tampering with the OS. You’re only pwned when using the phone after it has been manipulated.
Yeah I get it, it was just something I noticed. A pedantic lint, you could say.
I wanted to ask why it’s bad, what did you change?
Btw. the example function get_default is badly chosen, because unwrap_or_default exists.
Also ich hab vor 10 Tagen erst einen für 22,90€ bei welectron gekauft… Ist jetzt leider wieder etwas teurer, aber bekommen kann man schon wieder einen.
Der zero 2w ist doch ein sehr guter Kompromiss für Größe, Stromverbrauch und Preis.
Und gleiche Leistung für weniger Watt kann der Raspi 5 eventuell auch: Der Peozessor taktet bei 3A Netzteil automatisch runter und die Fertigungstechnik ist wesentlich neuer.
Generell finde ich die Raspberry Pis sehr nachhaltig. Klar, der Arbeitsspeicher ist verlötet. Dafür erhält man grandiose Software-Unterstützung und beliebige Erweiterbarkeit, da es eben ein bastelcomputer ist.
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.