> The worst part about USB-C is that it can be implemented so wrong it bricks your device! A Google engineer for a while was testing cables and not infrequently they worked poorly, not at all, or outright fried devices.
No spec is going to look good if you start blaming the spec when manufacturers sell things that don't conform to it. That is what the Google engineer found: these cables didn't conform to the spec. If you are going to do that then bricking the device is the least of your worries as USB is clearly to blame for this as well:
The real USB 3.2 issue is different. As a way of telling the user what they are buying, the USB 3.2 2x2 scheme is so bad it's almost comical. They could have insisted every device be marked with the maximum it actually supported. I guess they thought making something like this mandatory:
20G/3A/60W+dp+tb
for a device that supported 20G bit/sec, 3 amps and 30 watts with display port and thunderbolt pass through would use so much space there would be no place left for the market to earn their wages. Or something.
No spec is going to look good if you start blaming the spec when manufacturers sell things that don't conform to it. That is what the Google engineer found: these cables didn't conform to the spec. If you are going to do that then bricking the device is the least of your worries as USB is clearly to blame for this as well:
https://www.abc.net.au/news/2014-06-27/knock-off-usb-charger...
The real USB 3.2 issue is different. As a way of telling the user what they are buying, the USB 3.2 2x2 scheme is so bad it's almost comical. They could have insisted every device be marked with the maximum it actually supported. I guess they thought making something like this mandatory:
for a device that supported 20G bit/sec, 3 amps and 30 watts with display port and thunderbolt pass through would use so much space there would be no place left for the market to earn their wages. Or something.