2 ms·
Great example. First of all, we need dozen connectors. For network, for power, for special protocols, for special environments. No, USB-C doesn't cover it all,
by blacklion 2y ago
Great example. First of all, we need dozen connectors. For network, for power, for special protocols, for special environments. No, USB-C doesn't cover it all, from space station to miniature device which needs I2C or I2S connection, for example.
But lets look at USB-C alone*. It is USB-C, all USB-C is the same from the user-faced side. But they are different inside! There are a lot of variations, with different PCB footprint, different certification (aviation or automotive grade connectors vs "simple" ones), different weather protection, different mounting options. It is great that we have a LOT of different vendors for USB-C, and A LOT of different USB-C connectors!
USB-C is standard, with multiple vendors. As C/C++. One connector. Multiple vendors. Diversity.
[*] - and close eyes on situation with USB-C which is worse than ever, with all these functions which can or cannot be supported and you can never know what is support before trying, multiplied with same problem with myriad of cables which all look the same, but works differently. So, really, USB-C is bad example. But lets pretend it is good.
- wiseowise 2y agoYou’ve completely missed the analogy. As a user I couldn’t care less about all the bullshit innards of USB-C. All I care is that I can charge all my Android devices, all my iOS devices and my MacBooks with the same cable. As a developer I couldn’t care less whether it’s CMake, XMake, Gradle, Autotools, Bazel, Webpack, Bash script or something else. Is it standard? Is it not absolutely awful? Yes - let’s go, no: can you afford to pay devs to put up with learning yet another bullshit tool? Yes - let’s go, no - keep it to your hobby project until it reaches critical mass and becomes standard.