6 ms·
> 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 (
by 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]