5 ms·
The argument about bloatiness reads like a privileged position, IMO. Everyone is interested in getting customers with shitty 2G connections and tiny data caps,
by klodolph 9y ago
The argument about bloatiness reads like a privileged position, IMO. Everyone is interested in getting customers with shitty 2G connections and tiny data caps, because there literally billions of these people and nobody wants to bet that they're never going to have money to spend on your services.
If you pretend that all your users have net connections like the US, Europe, or parts of east Asia then you're going to end up as a small player in a balkanized internet. That's why all these companies are making aggressive investments and acquisitions in other parts of the world.
CDNs are also part of the fundamental reality of the internet. Could you imagine Netflix or YouTube without CDNs? The amount of network capacity investment necessary to run the internet as we know it without CDNs would cripple it.
And it's not just the internet, but it's a fundamental fact of computing that you have hierarchical caching layers with some data far away and some data closer.
- TeMPOraL 9y agoNo CDN is changing the fact that your website with 2MB worth of content and form weights 20MB and loads another 10MB of trackers. It's not about privilege or capturing emerging market. It's about laziness and waste, pure and simple. The same bloat that prevents someone from accessing your site on a smartphone in the middle of Africa is also significantly slowing down the computer of someone in western Europe, and eats into battery life too. And let's not bring streaming video into this as it's completely off-topic.
- klodolph 9y agoI've heard this argument before. Think about the people with shitty 2G connections and equally bad backhaul or backbone networks. The fact is these people are not necessarily as interested in your 2MB pages as you'd like. They have their own web pages and apps that they use. They do care about CDNs because some of these networks are just plain bad, and it's not the first hop. And that's the privileged position. Bloatiness is annoying if you're an American reading American pages, or a Spaniard reading Spanish pages, and we like to complain about it because it means the difference between being able to read an article on the subway and having to wait for the next stop. But I'm never in a position where I have to complain about the backhaul network or the backbone. In the future, please don't try to police "off-topic" conversation.
- ubernostrum 9y agoThe original point I made -- that Chrome's dev tools can simulate a slow network connection -- got nit-picked by people saying it can't figure out which CDN serves which ad bundle. This is not a useful, relevant or even coherent reply. Public web sites that only work for "first world internet" customers shouldn't be a thing. Sites that load 100MB of ads and trackers and fifty different JS frameworks to display a few paragraphs of text should be getting the search-engine death penalty until they clean up their act. They should be thinking about people who aren't on fast broadband connections. If they aren't, the search engines should be. YouTube learned this from the "paradoxical" result of a lighter-weight page increasing load times: http://blog.chriszacharias.com/page-weight-matters http://blog.chriszacharias.com/page-weight-matters (spoiler: it was because the lighter-weight page meant it was suddenly usable by people who had slow connections who couldn't use it previously, and those people began to use it, which skewed the average load time higher)
- ucaetano 9y ago> The original point I made -- that Chrome's dev tools can simulate a slow network connection -- got nit-picked by people saying it can't figure out which CDN serves which ad bundle. This is not a useful, relevant or even coherent reply. Let's say your website is hosted in Jakarta, and serves Indonesian customers. You make it lightweight and fast. Your competitor hosts its website from Singapore, and is much heavier. Now Google, from its datacenter in Singapore, wants to test the load times for your website and your competitor's. Sadly, the host you chose doesn't pay for a lot of international traffic on the cable to Singapore, since it primarily serves the Indonesian market. Google tests both sites, and your competitor's, based in Singapore about a mile away from the Google datacenter, loads several times faster, besides being heavier. Google ranks your competitor higher, and you are pissed off, as your customers load your site faster. Now another case: you and your competitor host your sites in Singapore. You build a lightweight site, and your competitor's is full of heavy assets, with oversized images, etc. Google tests both of your websites and yours loads faster, and is ranked higher. You're happy. But your competitor signs up for Akamai and replicates the heavy assets in local servers in all the major ISPs in Indonesia. Customers in Indonesia search and see both your and your competitor's results. You rank higher and get more clicks, but as your traffic is subject to the congestion on the international cables, your site actually loads far slower than your lower-ranked and heavier competitor. Customers are unhappy. In all of this, simulating a slow connection on Chrome's dev tools is irrelevant, because you don't know where the bottleneck is!