3 ms·
This seems to be an unpopular opinion, but I generally agree and see latency (within reason) as a UX problem more often than not. A lot of the folks I talk to
by mmcclure 8y ago
This seems to be an unpopular opinion, but I generally agree and see latency (within reason) as a UX problem more often than not.
A lot of the folks I talk to that think they desperately need sub 5 second latency would most likely be completely fine with ~15 seconds with a few minor UX/UI considerations. Since true low latency is fraught with scaling issues or is obscenely expensive, I think that leads to a lot of folks never actually getting ideas off the ground when they could have just hacked something together (cheaply) using off the shelf technology with "normal" latency in a few hours.
That being said there definitely are use cases for low latency and a lot of products/projects would benefit from it, but I don't think it's the hard, upfront requirement a lot of folks see it as.
Edit: For the sake of disclosure, I'm one of the Mux founders and we're currently working on low latency, but haven't released anything yet.
- Wowfunhappy 8y ago> This seems to be an unpopular opinion, but I generally agree and see latency (within reason) as a UX problem more often than not. It is a UX problem. One that can be solved by lowering the latency. Many examples of latency being a problem have been mentioned in the comments here, not to mention the article: sporting events ruined because your neighbor cheered too early, reading tweets about the State of the Union before it appears on your feed, etc etc. How do you improve this without actually decreasing latency?
- imtringued 8y agoSweep the problem under the rug. Delay everything by the highest latency. Let everyone suffer equally! (this is what bluetooth audio does)