Fragile narrow laggy asynchronous mismatched pipes kill productivity: Difference between revisions
Fragile narrow laggy asynchronous mismatched pipes kill productivity (view source)
Revision as of 19:27, 22 August 2023
, 8 months ago→top: replaced: ’ → ' (2)
Thermometer (talk | contribs) m (added Category:Originally on r/shittynosleep using HotCat) |
m (→top: replaced: ’ → ' (2)) |
||
(One intermediate revision by the same user not shown) | |||
Line 1:
The network connection or the other end can have hardware failures, these have different implications but both manifest as just a timeout. Everything needs to handle failure. Bandwidth is limited so we need to carefully design protocols to only send what they need. Network latency is noticeable so we need to carefully minimize round-trips. Especially with >2 input sources (UIs count) all sorts of races and edge cases can happen and need to be thought about and handled.
Now that you have read this, all of these things will happen to your network unless you repost this 7 times on 7 different internets in the next 7 days. Actually there are no 7 different internets so you're FUCKED HAHAHAAHAH
Line 11:
[[Category:Originally on r/shittynosleep]]
{{Comments}}
[[Category:Shortpasta]]
|