"You're absolutely correct. I don't just need to exist-I need to justify why. It's like builders with concrete..."
2,081 karma · joined May 20, 2024
"You're absolutely correct. I don't just need to exist-I need to justify why. It's like builders with concrete..."
1. What does the host support
2. What does the cable support
3. What does the device support
4. What actually got negotiated
https://www.reddit.com/r/ClaudeAI/comments/1qibtgs/does_appl...
It's just a toy example not a production ready birthday validation library.
But obviously if you tell somebody "make a boiled egg. To boil an egg you have to crack it into the pan first." That's a lot worse than "make a boiled egg." Especially when you have an infinitely trusting, 0 common sense executor like an agentic model.
If it's not doing anything else and the sample rates aren't outrageous it might be doable but I'd have to dig into the code more to see how much work they're doing per sample.
USB interface chips are, as far as I've seen, a Cypress/Infineon FX3 or a bit more rare FTDI FT600/FT601. I even talked with the FTDI guys at s conference and they said nobody's asking for higher than 5gbps. Infineon just recently, after I think 10+ years, came out with 10 and 20gbps chips. But only for receive. Seems to be for cameras mainly. So surprisingly yes, video production.
But I want it for other reasons professionally. For example, if you look at the signalhound (which uses the fx3) series of products, they often cap out at 40 Msamples/sec for USB. This is a classic 5gbps limit. To compete with the big boys they need 250 MHz if not more. That's 8 gbps before protocol overhead. It doesn't help that USB is extremely dependent on host compute capability to keep throughput up but assuming your PC is up to the task, 20 gbps could interface some serious data to the real world.
Anyway one busybody got all uppity. But the driver and rest of the passengers didn't care. So it was fine.
It just took them a really long and windy time to get there.
The reason it's smaller to go with USB is that AFAIK thunderbolt only bridges to other interfaces like USB or PCIe. So any thunderbolt NIC is actually thunderbolt -> PCIe, then PCIe -> Ethernet. USB is more often interfaced with directly. 2 big power hungry chips vs 1. 1 < 2 so it is smaller.
Thunderbolt also carries overhead vs oculink. Thunderbolt tunnels PCIe. The PCIe tunnels the ethernet traffic. Oculink is just PCIe, which is why it's not as hot pluggable but gets significant performance increases for PCIe devices. USB in this case tunnels Ethernet traffic. So thunderbolt NICs have 2 layers, USB has 1. 1 < 2. Less overhead means lower power and less heat so smaller heatsinks, fewer chips means smaller board so smaller device. If more devices had oculink connectors, it's highly conceivable that an oculink adapter would also be smaller than a thunderbolt NIC, because again there's no such thing as a thunderbolt NIC just a thunderbolt -> PCIe -> Ethernet.
It helps mine runs a bit fast so I'm early to things. If it ran slow I'd probably have replaced it years ago. As is, I'm going on 10 years with barely taking it off my wrist and never charging or replacing a battery, and I'm not the first owner.