![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.dbzer0.com/pictrs/image/a18b0c69-23c9-4b2a-b8e0-3aca0172390d.png)
at least on a 4, this command will misleadingly return “disabled” even though your programs are able to use hwdec, because the h.265 decoder isn’t part of the Pi 4’s GPU, it’s elsewhere.
at least on a 4, this command will misleadingly return “disabled” even though your programs are able to use hwdec, because the h.265 decoder isn’t part of the Pi 4’s GPU, it’s elsewhere.
Freezing temperatures being obvious with a minus number is an advantage, not a problem, IMO. Easy to see from the bigger negative number when water will freeze more quickly, when snow is more likely to lie on the ground, etc.
americans really just have to remember a long list of random numbers like how many ounces a full pint is supposed to be, huh.
i’m imagining a whole day of school like, “when people say nickel, they mean 5 cents, a dime is 10 cents, 12 inches is a foot, 3 feet is a yard, water freezes at 32F and boils at 212F…” and the children just crying into their notebooks by the time they get to miles and tons and acres.
So… do they need external cracks?
“indentation is indentation!” (mr_incredible_cereal.jpg)
it may look messy, but would you actually rather Python didn’t support some inconsistency when the intent is clear?
being exact just for the sake of being pedantic isn’t useful.
“the punchline is clearly trivial, the set-up is left as an exercise for the reader”
nor decoding 264 :(
a rather annoying regression from the 4 to the 5, especially when the 5 now supports more MIPI cameras where live encoding is crucial.