> Speaking of a recipe for disaster. Let’s say you made the mistake of using UDP directly because you want them datagrams. You’re bound to mess up, and you won’t even realize why.
>
> If you want to build your own transport protocol on top of UDP, you “need” to implement:
> 
> - retransmissions
> - congestion control

> And if you want a great protocol, you also need:
> 
> - encryption
> - RTT estimates
> - path validation
> - path migration
> - pacing
> - flow control
> - version negotiation
> - extensions
> - prioritization
> - keep-alives
> - multiplexing

lol my post-college job was at a company that did this, rolling all of it on their own, and built products around it primarily geared toward sending huge files over the internet. They sold to IBM at the perfect time, right before [QUIC](https://en.wikipedia.org/wiki/QUIC) started seeing real world usage. 

k00b

tech

This link was posted by [wofo](https://news.ycombinator.com/user?id=wofo) 1 hour ago on [HN](https://news.ycombinator.com/item?id=40766079). It received 53 points and 39 comments.