This is on Nintendo being jerks. Just because web server X doesn't implement the standard correctly, that does not make TCP or HTTP bad.

No, but the average consumer doesn't care who's actually at fault. They're just confused when their stuff doesn't work/is flaky. There is a difference between the standard in theory and the standard in practice, and I've seen a remarkable number of ordinary people very confused about whether various things actually work with each other, and a lot of it out in the real world is very poorly communicated and out-of-spec.

Note that most bricking was with 3rd party docks (due to the Switch not so standard conform HDMIish + charging alternate mode).

Bricking your switch with a "pure" charger mostly only happens with but fully standard conform chargers used with the wrong cable.

Most (all?) Hight voltage/amper chargers like e.g. for laptops work just fine on the switch.

Through it's a bit more troublesome for the dock.

Why are they saying 'bricked' when they mean they were destroyed? 'Bricking' is normally a firmware issue.

Do we say that a car was 'bricked' when we trash it in an accident?

Bricking is generally considered to be invisible destruction that renders a device useless but still cosmetically intact. People used to call these things paperweights with a hint of irony because there are lots of fancy paperweight designs. Nowadays people view such devices to be as useful as bricks. They are heavy and take up space but they are still intact and jokingly enough you could actually use them as construction material.

A car that was destroyed in an accident would not be considered bricked because it has sustained cosmetic damage. You can't use it for it's aesthetics alone. e.g. in a museum. A Tesla car where the battery charger has died could be considered a bricked car though.