Earlier quoted context omitted.
The internet traditionally uses location-addressing. A DNS name pointing to a IP which has a specific location your computer tries to reach in order to fetch the content. This means that particular node needs to respond to you, and the bandwidth is depending on the bandwidth available on the particular path to that specific node. Instead, IPFS uses content-addressing, where the content is hashed and given a ID based…
Caches solve this placement problem just fine today and content addressing does not alleviate the placement problem at all. Reality is the space thing is just part of the usual crypto grift narrative building.
Being able to arbitrary place caches anywhere and let anyone serve the data, and you can trust you're getting the right data, is a huge benefit over location-addressing. Ignoring IPFS, content-addressing makes sense for so many things, which is what lots of storage/caching/CDN solutions have discovered decades ago.
Content-addressing is nothing new (nor did Protocol Labs/IPFS "invent" it) and if you're using a CDN to serve content today, the CDN is with 99% certainty using content-addressing at least internally.