4 ms·
I can't decide how I feel about this. On the one hand, they are totally right that polling is an inelegant solution. In the context of a large-scale website, pe
by sholladay 7y ago
I can't decide how I feel about this. On the one hand, they are totally right that polling is an inelegant solution. In the context of a large-scale website, perhaps it is even harmful to a degree that we should take special note of it. On the other hand, however, the amount of time that was spent on trashing this work is sad to me. Polling is not merely a quick and dirty solution, it is a high-reliability solution where other techniques may fail. I have used many proxies that don't handle WebSockets properly, for example. It is not simple to maintain long-lived streams or connections across all networks. So there are practical upsides to polling that should not be ignored. I can appreciate that this post goes into details explaining why polling is bad, but perhaps it would have come across better as a tweet or something, rather than a full blog post with fancy charts showing how much a particular project sucks.
- unilynx 7y agoExactly - poll `/status.json?at=${Date.now() - Date.now() % 5000}` and let the CDN worry about infinitely distributing state. (and make sure the CDN isn't caching 404s triggered by clients who are already in the future)