That's a possibility. Some code still assumes (without realizing!) x86 style ordered loads and stores. This is called a strong memory model, specifically TSO, Total Store Order. If you tell x86 to execute "a=1; b=2;", it will always store value to 'a' first. Of course compilers might reorder stores and loads, but that's another matter.
ARM is free to reorder stores and loads. This is called a weak memory model. So unless it's explicitly told to the compiler, like C++ memory_order::acquire and memory_order::release, you might get invalid behavior. Heisenbugs in the worst case.
I wonder why he didn't use a RP2350, it costs practically same as the older RP2040. That way it could have 450 kB or so system RAM, enough to play around with some old productivity software.
Very much simplified, a 10 minute charge would mean 6C charging throughout the curve. 100 kWh battery would thus require 600 kW on average. Right now the most powerful MCS chargers deliver 1440 kW.
So not impossible, as long as the battery can handle the current. It's obvious that charging technology is not going to be the bottleneck.
(A real battery would probably have a charging curve that slows down towards the end, so more than 6C would be required in realistic conditions.)
> My Tesla has no clue at all that that's happening. And worse, the perpendicular camera responsible for checking cross-traffic is mounted _behind my head_ on the b-pillar
It has a wide angle camera in front that you usually can never see outside service menu. It should cover that case.
> Tesla's forward facing cameras are effectively monocular
Notably, human perception is effectively monocular in driving situations at distances of 60 feet or farther. It's best in the area where your limbs can reach.
"precise" stereo vision is 30m, but the limit of depth perception is around 200m (some people are 500m)
crucially we have excellent implied depth, and object detection, something that even non-realtime state of the art tracking doesn't have.
human depth is much more complex than just parallax, which some poeple use as an argument that "pure vision" monocular depth is possible to do robustly. It will be, but not for a while. Especially as depth is only part of the problem. object categorisation is the other.
There's some truth to what the gp said. Some hydrogen will escape, enter the upper atmosphere, and be blown away by the solar wind and thus be permanently lost.
I assume that this has been happening to all gases in the atmosphere for aeons, and thus, while technically correct, it is completely negligible for the relevant time scale.
ARM is free to reorder stores and loads. This is called a weak memory model. So unless it's explicitly told to the compiler, like C++ memory_order::acquire and memory_order::release, you might get invalid behavior. Heisenbugs in the worst case.
reply