|
|
|
|
|
by dghlsakjg
1135 days ago
|
|
As someone who designs device, I would HATE having to use a proprietary connector/device/protocol. I'm small time, so maybe engineering departments at major companies see it differently. Right now I can design a product that uses one of the USB standards and pick from literally thousands of different pre-made parts that handle all the silly things for me. If I'm fine with 5v/2a power, I can just drop a $.0292 (that's the prototype price, it drops drastically at higher volumes) piece into the design and know that any cable and charger will work with it. If I need more power than 10 watts I can spend $.50 on a usb-c plug and PD controller. I truly don't understand why companies would fight this for most devices. The one thing I'm worried about is what happens when someone comes up with something truly innovative (say, a phone battery that can charge at faster than 100 watts). Does that mean they will be penalized if they have to use a proprietary connector since usb-c is unable to meet that? |
|
We already have, though, a glut of the pre-made components you talk about that cut every corner as close as they can-hopefully not so far as to start a fire, because you can’t sell to dead customers, but up to then? Go for it.
The number of implementations of PD has been a mess, with various chunks of a particular profile unavailable, inconsistently, along with no meaningful distinction between various versions of PD on most devices. Cables are often trash, and there is no certification for them required at all, until you get up to the point that Intel will smack you with a folder of lawyers if you try to call something a Thunderbolt cable without getting it certified. So we can all go out and buy just Thunderbolt cables and be sure it’ll work with everything else, and it’s all well and good until our wallet notices the hit.
Surely it can’t be that hard to just … check that stuff meets the standard, as in cGMP-style adapted to electronics (to the extent it isn’t already). Right?