It was actually pretty great when I worked for a company making things here in england:
“That needs to move 50cm” meant it had to move exactly 500mm
“That needs to move a foot” meant just kick it over about a foot

It was just an unspoken thing that metric meant precise and imperial was just caveman measuring

Got into making redstone logic in Minecraft, including joining a community of people building all kinds of crazy things like CPUs. This was early days too - I think the repeater was brand new

Eventually wanted to make mods so started learning Java. Was bad at it. Then wanted to make games in unity. Was bad at it. Learned C++ at Uni. Dropped out and was bad at it.

Kind of repeated this cycle for various languages and tools for years, never with enough motivation to learn properly. Eventually I hit a critical mass of skill and was able to actually make things in HTML/JS and over a couple years this snowballs until surprisingly quickly I find myself a senior developer teaching others!

Assuming a ground clearance of 10cm, and a wheelbase of 2.4m (source: my ass) then you can construct an arc under the wheels

This arc says you could drive such a car on an earth with radius as small as 7.25m. Actually, it could be slightly smaller because of where the wheels would contact, but I’ve lost interest

It’s not stateless end-to-end, it just means the client needs to keep track and pass the state rather than drivers or hardware

I’m not 100% on the motivation but from an architectural standpoint it does make sense - your software can now do many new and weird things without a hardware change

One example I saw was allowing an arbitrary number of streams to be processed simultaneously, just passing the different context state for each stream