Yeh, probably sucks for a lot of disabled people as well.
As a tall person myself, I have used similar and haven't had an issue. But there are taller people than me, so maybe I am not tall enough.
Bus stop benches are also horrible. As are most seats in fast food restaurants. Airplane seats are also too small.
Some seats aren't meant for a long time of sitting, or have other priorities I guess.

There is also only 1. Not great if you need a break at the same time someone else does.

I develop in containers, which means I don't have to install dependencies on my host.
While it's overhead, it's never that massive.
Sure things like Codium and all the tooling takes up a lot of memory... I don't think I've seen over 10gb of "dev related" memory.
I feel like people are significantly desensitized about how much data 1GB actually is.

I hope everyone uses this new UDP thing!

It has a seat.
You go in, sit down and rest a little.

I've seen them at big conferences and big offices (although, most are private pods for work, some offices do have little private/quiet booths for sitting in).

Humans ARE the resource

Just 2 alphas doing alpha things

Of course Brits don't want to become a minority in their home country... who would? We all know how badly they are treated

Absolutely wild comment.

I'd rather have a more ambiguous name that is clarified by context than comments or docs.
create(obj) is useless, but if it is namespaces and properly typed user.create(User user) makes a LOT more sense.
Granted, that is a very narrow example, but it gets the point across: let context carry context, and use it properly.
Something like import {create} from 'user' (and using it with merely create()) is less useful that import * from 'user' (and using it as user.create())

We namespace things to help split up code. Lean on the namespaces when using that code!

Usama Arif found that with the three patches to just probe BMI2 CPU support only once, it yield a 71% reduction in decompression time and a 18% reduction in compression time for a crypto_acomp benchmark.

Wow

It's not really the wattage that's an issue.
If it ran at 600 volts, it would only be 1 amp.

But at 12v, it's 50 amps of current.
Which is a lot.
And it's not massively peaky/bursty, so it needs to withstand that constantly.
Pretty sure something like 10-15mm² cross section of copper is needed for that, which is a thick cable.

But, this is also a problem that has been solved elsewhere. For whatever reason, manufacturers have settled in a terrible solution.

Both can be true. Both should be true

I don't think people care about it, but it seems to trigger some subconscious "I'm too close" and they drop back a bit.

I guess if someone is actually being an asshole aggressive tailgater then they won't care