You say the article is bad advice and then proceed to give extremely nitpicky but ultimately similar advice: UDP is _this_ kind of optimization(latency) and not

You say the article is bad advice and then proceed to give extremely nitpicky but ultimately similar advice: UDP is _this_ kind of optimization(latency) and not _that_ kind of optimization(throughput). Which is really attempting to strawman the article based on some notes tucked into its closing paragraphs, when the central point is passages like: > In testing, on your LAN, on lo0, when there's not a lot going on in the game, delivery is totally reliable, so the code path for recovering from missed datagrams is never covered, the usability where users are dealing with lost traffic is never stressed. That is some damn sound engineering advice right there: build when you have the test case. Don't whip yourself into a frenzy over it prematurely.