And if you got in a car and drove against the direction of spin you would become lighter. While if you went with the direction of spin you would become heavier.
Try working for them. I've worked for a lot of businesses outside of IT and every single one had problems that could be solved with software. Not all of them were viable business opportunities but some of them were huge.
Actually selling them solutions is difficult though because management is often too stupid to understand it no matter how simple the solution. Plus often management doesn't actually care if they are throwing money away. So long as they think they are up to date with industry norms in the region they operate then they feel like they are doing their job. I've proposed solutions that similar companies use in other countries successfully and been met with complete disinterest. YMMV
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.
An operating system built around IPFS. This would make the browser/native dichotomy irrelevant by offering the best of both worlds and then some.
AFAIK the reason web apps have become so popular is because they load quickly and don't require the user to manage installation and updating. IPFS would achieve the speed through caching and the installing/updating process with its namespaces feature.
An OS based on IPFS would give you the best of both worlds.
AFAIK browsers are popular because they load apps quickly and without an install step. While native apps let you choose your stack. An OS based on IPFS would load big apps quickly thanks to caching, the install step would go away because there is no difference between remote files and local ones and its still an OS so the app can be written in C or any other language built on top of it.