5 ms·
Oh boo hoo they enumerated an enormous number of corner cases, handled backwards compatibility, crappy cables, all sorts of things. It also reflects decades of
by gumby 8y ago
Oh boo hoo they enumerated an enormous number of corner cases, handled backwards compatibility, crappy cables, all sorts of things. It also reflects decades of back compatibility and painfully learned mistakes (consider mini-A) not to mention some weird pathologies (weird naming like hi-speed/ full-speed/ super-speed).
It sucks that the standard is so complex that a small number of design houses and consulting shops will end up with a de facto cartel of understanding the Sacred Knowledge, but nobody's stopping you coming up to speed by reading the whole spec and doing a lot of implementing. But it's not like you can build a solid TCP stack these days either simply by reading the original late 70s RFCs.
And you don't have to use this spec -- you can still use RS-449 if you think the USB spec has become overly complex. In fact I used that in a design only a few years ago!
- whitequark_ 8y ago> But it's not like you can build a solid TCP stack these days either simply by reading the original late 70s RFCs. I literally did this. It's called smoltcp (https://github.com/m-labs/smoltcp https://github.com/m-labs/smoltcp) and we use it in production as an lwIP replacement with great results.
- kachnuv_ocasek 8y agoI love Hacker News. I was just looking for this library to use in my embedded toy.
- adiusmus 8y ago‘You can’t.” ‘You can and I have running code”. This is why HN is great.
- etaioinshrdlu 8y agoI think it would be cool if a project had a self-imposed token count limit. The project would never be allowed to grow more than X tokens long. Then you can guarantee the project is small and haiku-like forever! LWIP started off small, and it grew...
- whitequark_ 8y agoThe "smol" in "smoltcp" is mostly talking about the internal architecture and exposed API. For example, it will never support true zero-copy sockets, because the API burden due to restricting itself to safe Rust is too high. I don't think any TCP/IP implementation is going to be "haiku-like", the protocol stack is way too messy.
- andrewflnr 8y agoDoes it work reliably on the open internet? AIUI, it's interoperability with all the edge cases of badly implemented protocols that leads to statements like GPs.
- deleted 8y ago[deleted]