USB-C cables can be a mess. One cable charges at 5W, another does 100W and Thunderbolt 4, and they look identical in the drawer.
WhatCable sits in your menu bar and reads the cable data your Mac already has access to. Plug in a cable and it tells you in plain English what it can actually do: charging wattage, data speed, display support, Thunderbolt, etc.
Built in Swift/SwiftUI. Open source, free, no tracking.

Discussion (50 Comments)Read Original on HackerNews
Just wanted to say this because I feel it's really crazy that I can just do this today...
Although I imagine if you don't have the motivation to make it in the first place, you likely don't have the motivation to package it.
How is this conducive to the typical usage pattern of an app like this?
Well, I can think of one reason why it wasn't that much more trouble. François Chollet had a nice tweet [1] on why removing human cognitive friction is resulting in needless software complexity.
[0] https://github.com/darrylmorley/whatcable/blob/main/Sources/...
[1] https://x.com/fchollet/status/2045929951539707957
If so, it feels like a needlessly indirect and combative way to go about it.
https://news.ycombinator.com/item?id=47973621
P.S. Some time ago I learnt through HN of a one-line command in macOS which revealed the power (Wattage) of the connected charger. Can't find it now, but it was very useful.
1. What does the host support
2. What does the cable support
3. What does the device support
4. What actually got negotiated
You know you can close it? :-)
That's all the program is telling you. It doesn't matter that it's backwards, but technically it is.
WhatCable says "No USB-C Ports Detected".
System info clearly shows my iPhone attached to USB 3.1 Bus.
It just tell you want the e-marker said.
That should be mandatory.
I like this tool, but I agree that it was rushed and it is still being rushed. I urge the developer to slow down and get it right.
Shipping early is an entirely valid dev strategy.