Performance: With HTTP you have to constantly check if what you have cached is up to date because it could change. And a bunch of other little performance advantages.
Immutability: with HTTP you have to save things you care about because they might disappear/move in the future. With IPFS you could pretty much always rely on at least Google holding a copy of something in the long term.
Basically the idea is to remove the concept of local vs remote files at the OS level. So as a user of the OS the file browser and the web browser are the same application. They shouldn't even be able to tell if something is on their computer or not. This could be implemented on HTTP but only as a prototype.
Immutability: with HTTP you have to save things you care about because they might disappear/move in the future. With IPFS you could pretty much always rely on at least Google holding a copy of something in the long term.
Basically the idea is to remove the concept of local vs remote files at the OS level. So as a user of the OS the file browser and the web browser are the same application. They shouldn't even be able to tell if something is on their computer or not. This could be implemented on HTTP but only as a prototype.