fox wrote:I mean, I too switch between hundreds of devices daily to do development and stuff, and am being very angry about all those literal precious seconds of my life I'm permanently losing to Dojo loading because my development server is on a dialup modem, as opposed to CDN to which I am connected through a direct neural interface.
i already pointed out in the recent bug that high bandwidth is not the same thing low latency. having a tt-rss instance that is physically far away (and thus high latency) even if both client & server have otherwise good connections (high bandwidth and low latency to local connections) means each serialized connection is painful. using a CDN that is physically close to you (which works even whilst traveling) helps out, not to mention the CDN in this case is almost guaranteed to have faster hardware & network connection than your server.
SPDY certainly mitigates that to a degree, but that is not easily deployable for many people today on the server side (or even possible depending on your hosting), nor do all clients support it. thus we are left with classic web optimization tricks like leveraging multiple domains and CDNs.
unfortunately you dismiss such real world use cases out of hand. i'll just keep it in my fork and move on.