I'm under the impression that the original comment was referring to an IPFS-powered web, rather than the web being powered by IPFS. Good ol' HTTP servers will continue to form the web as we know it, and IPFS can provide a new web of static content.
Re:IPFS Project Roadmap
by IgorPartola on Friday April 12, 2019 @08:29PM
(#19650246)
So at best IPFS is a replacement for something like S3? If I want to create an application, I can have the static content portion of it hosted on IPFS, but the brunt still on my own servers? That’s a very niche use case, I would say. And while it allows me to host my copy of the anarchist’s cookbook, it’s not going to be good for much else.
I didn't say it's everything. I don't think HTTP must die or will die. HTTP is great, it's awesome, wonderful. I would like IPFS to exist along with HTTP, that's what I said.
Actually, I think the fact that IPFS developers are trying to replace HTTP one of the reasons they fail so awfully in producing a good IPFS for static content. They try to integrate much more stuff than actually needed in the protocol.
I don't want to hijack the discussion from IPFS, but Swarm has good ideas with respect to dynamic content if you're interested how that might work in a decentralized setting, for example see Swarm Feeds presented here: https://www.youtube.com/watch?v=92PtA5vRMl8
Now, obviously, they're under no obligation to deliver anything. But I'm trying to understand what you mean when you say:
Only handling the static part of webhosting is something, but it's not everything.