Here's an interesting blog post that warns that the new USB-c/Thunderbolt 3 port technology is full of hidden perils -- especially where the right cables/dongles are concerned:
http://blog.fosketts.net/2016/10/29/total-nightmare-usb-c-thunderbolt-3/
Just an observation on my part, but traditionally Apple's cables/dongles (as well as those from other companies) have been poorly marked insofar as "identification purposes" are concerned. In other words, there's very little marking on the cable/adapter/dongle that identifies exactly -what it's for-. Sometimes there's a cryptic icon, which itself can be hard to see.
The advent of USB-c/Thunderbolt 3, makes it critical to use the right adapter for the application-at-hand. For this reason, I'd like to see adapters/dongles more clearly labeled so that even an old guy like me can easily identify for what purpose they're intended.
This goes against Apple's longtime policy that style overrides function. But with the introduction of a "one port to do it all", it becomes more important that users be able to identify what connecting components they need, to avoid connection mistakes (and disasters) as the blog writer describes above...
http://blog.fosketts.net/2016/10/29/total-nightmare-usb-c-thunderbolt-3/
Just an observation on my part, but traditionally Apple's cables/dongles (as well as those from other companies) have been poorly marked insofar as "identification purposes" are concerned. In other words, there's very little marking on the cable/adapter/dongle that identifies exactly -what it's for-. Sometimes there's a cryptic icon, which itself can be hard to see.
The advent of USB-c/Thunderbolt 3, makes it critical to use the right adapter for the application-at-hand. For this reason, I'd like to see adapters/dongles more clearly labeled so that even an old guy like me can easily identify for what purpose they're intended.
This goes against Apple's longtime policy that style overrides function. But with the introduction of a "one port to do it all", it becomes more important that users be able to identify what connecting components they need, to avoid connection mistakes (and disasters) as the blog writer describes above...
