I like the idea of storing data and apps locally!
Lets take a fun game. How about all of Atari 2600?
https://ipfs.io/ipfs/QmacAqRVhJX9eS7YJX1vY3ifFKF9CduDqPEgaCU...
Ok.. This is remote, across all the machines that have that IPFS hash. In other words, its not local.
(in console) ipfs pin add QmacAqRVhJX9eS7YJX1vY3ifFKF9CduDqPEgaCUSa4x5xb
Now its local!
Or lets do something more than a game... How about Node-Red in browser(PageNodes)?
http://ipfs.io/ipfs/QmSCrZUPkqH4gsncsD7tGXPiFpymsbwmywsHXLDh...
EDIT: I had the point in my head, but didn't put it down here. In other words, we already have this technology, and not using buzzword-bingo like "Its the interwebz but with blockchains!". These links are direct proof that it not only exists, but is working right now.
And in reality, making a type of blockchain in IPFS would not be hard. It's an immutable data structure, with append-only characteristics.
And, I also am partial to IPFS, primarily because it feels like a proper IETF-internet scale project. ZeroNET looks prettier, but.. throw away. Again, some subjective feel there, but IPFS feels elegant.
Primarily, I see ZeroNET as its competitor. And ZeroNET has the bling and the wow factor, but much of the underlying system is.. unfinished. It also requires some heafty frontend with backing DB as well. It seems cobbled on and over-engineered.
IPFS, on the other hand, is clean and clear of its focus. It's simple enough to do as it purports. It works now. It seamlessly works with gateways to allow non-IPFS users to access the network. It's network agnostic: ip4, 6, and whatever else is a protocol addon. And it seems to be on its way to an IETF standard.
ipfs is a decent storage system, but i think there are better ways to model applications for a decentralized world.
Blockstack provides naming, identity and security (you know what public key is connected to "myname.id").