It’s hard to answer without specifics but languages shouldn’t require you to determine whether it’s safe to use an api in an async context or whether it will hang your app. I imagine some of the sharp edges you might have run into are because go has real parallelism and you have to address data sharing.
This is fantastic progress for CPython. I had almost given up hope that CPython would overcome the GIL after first hitting its limitations over 10 years ago.
That being said I strongly believe that because of the sharp edges on async style code vs proper co-routine-based user threads like go-routines and Java virtual threads Python is still far behind optimal parallelism patterns.
TR in the US makes sockets harder to use, but I have never heard anyone complain about TR in the UK, as the earth/ground pin is always present, and is physically longer than the live and neutral, so mechanically it is reliable and unnoticeable.
“Just baby proof” means remembering to keep those little plastic covers in place in every outlet. That doesn’t seem like superior usability.
The shutter prevents someone (including children) shoving something metal into the live/hot. I have never heard of it failing. Newer US outlets (TR/tamper resistant) are way more finicky because of the optional ground pin. Sticking the little plastic covers over the outlet is a workaround.
The reason for a fuse is because of the high current capacity of ring circuits vs branch/radial. The fuse protects the power cable of appliances catching fire as they can’t handle the current available on the circuit .
Ring circuits are a thing due to minimizing copper usage when rebuilding after ww2.
It at least has the virtualization framework now. There’s a product called Anka that plugs into Jenkins and lets you deploy macOS VM images as build agents on top of physical Apple hardware. While slower than containers, and limited to 2 VMs (?!?) you can have reproducible and sane build environments via VM images.
Pump filling times should be compared with DC-fast charging times as L2 is normally what you do at home when you don’t care too much about how long it takes. F150 will DC fast charge 15% -> 80% in “around 32 minutes”. Level 2 takes 10 hours as you point out.
While it’s more how they are used, imo optional is abused to the point it adds complexity. You don’t avoid handling null, but now you have to deal with present or not. Therefore you’ve gone from 2 states to 3. Use of value or null is simpler to me and use of optional can be via Optional.of() rather than parameters and properties for the vast majority of cases.
I always choose the “essential cookies only” option. This is normally harder than accepting all cookies, but it is getting easier over time. I rarely see a site that has essential-only.