14 ms·
I think a huge problem with usb-c is that there's software lacking explaining the situation to the user. There exist a huge number of standards and options but
by LeanderK 5y ago
I think a huge problem with usb-c is that there's software lacking explaining the situation to the user. There exist a huge number of standards and options but for users it only works or it doesn't, but ideally it should be explained in an easy way. For example with power-delivery: I need X watt, you charger can provide it but the cable can only handle up to Y Watt. Identifying what's at fault, why and what to do.
Can one just write an app like this? For an macbook, the information should be there....although it sounds very, very complicated and involved.
- ct0 5y agoOne of my favorite subreddits answers many of these questions, or at least tries to. https://old.reddit.com/r/UsbCHardware/ https://old.reddit.com/r/UsbCHardware/
- deleted 5y ago[deleted]
- SAI_Peregrinus 5y agoI think they mean it should show up as part of the error message provided by the OS. "Error, the cable you used to connect <human-readable monitor identifier> doesn't support <thing needed>." "Error, the dock <human-readable dock identifier> doesn't support <thing needed>, which <human-readable peripheral identifier> requires." Identify the limiting component, explain the what the new cable/dock/hub/etc needs to support so the customer has an actual chance of getting things to work!
- LeanderK 5y agoyeah, that's what I mean! The OS should explain the situation.