.24 Watt-hours is 864 Watts for one second, so a 100W human takes ~9 seconds for that output.
.24 Watt-hours is 864 Watts for one second, so a 100W human takes ~9 seconds for that output.
What is supposed to happen? The US and vehicle makers doubles down on ICE cars while the rest of the world moves in the other direction?
Sounds like a good way to trash any competitiveness US car makers have....
I was driving on a two-lane highway and saw a deer up ahead on the side of the road so I started slowing down. The deer saw me, panicked and ran into the brush/woods, then changed direction and ran out and back toward the highway. I kept slowing. It changed direction and ran back toward the woods, changed direction again and ran back toward the highway. By now I was at a full stop and parallel to the deer. It ran head first into the side of my truck, fell down, got up and sort of stumbled back into the woods…
You can say that people should know better but sometimes dead tree maps are not available, and anyway there’s no doubt that they are on the way out. The “safe/reliable” way might even seem to be up for debate, since phones can be more waterproof than paper, less likely to blow away when you’re on top of a mountain, serve as a backup flashlight/emergency comms, etc. But all it takes is a company that decides to force auto update and a PM that decides feature churn increases engagement and creates job security, and who knows what will break?
It is kind of like packaging that’s a choking or asphyxiation hazard.. if you’re doing anything that affects millions of people, it’s almost ALWAYS a safety issue even if you don’t usually think of it that way. No big audience or big user base without big responsibilities. Sure you’ll probably not be held liable in law suits, but on the other hand you should probably feel bad if you’re killing people due to indifference /negligence when thinking through edge cases.
GaiaGPS, which advertises is offline capability, after an update (but not immediately after the update) recently required users to login to continue using the app. Which was impossible if you happened to be out of cell phone range 10 miles from a trailhead when this login popup happened. Incredibly bone-headed move, and dangerous for hikers that aren't smart enough to carry backup map sources. But Gaia has been trending this way for several years.
In the last 3 months, NextDNS has blocked nearly 9% of 10M DNS queries from devices in my household with no ill effects that I'm aware of. (I'm not affiliated with NextDNS in any way, other than as a satisfied paying customer.)
Happy to answer any questions! And here are a couple of scattered thoughts:
* I'm really interested in what this looks like if you use animations (firefox supports animated favicons) - I could, for example, anticipate future ball positions and create animated SVGs to get a much nicer framerate.
* A friend pointed out offline that canvas rasterization (typically) is on the GPU, which is probably why my performance intuitions with my stuttering animation were so wrong
* I am only moderately confident that chrome caps favicon updates to 4 a second; I know there are a lot of different ways to update favicons and I could have missed something here!
I worry this move to homeschooling and micromanaging children's social lives just creates bubbles and makes children incapable of interacting with those outside of them.