The problem is that the blockchain substrate you're talking about is actually a very poor fit for decentralized applications. Let's compare it to it's earliest

The problem is that the blockchain substrate you're talking about is actually a very poor fit for decentralized applications. Let's compare it to it's earliest predecessor technology: Git[0]. This is a very useful technology within the problem domain of how to store and synchronize source code repositories (although it's UI sucks). However, individual users still need to choose who to synchronize with and what commits to accept. What blockchains add are restrictions to this model that make sense for the problem domain of digital currency: namely, you need to burn energy in order to commit, and you have to follow specific validity rules in order for your commit to be valid. These rules are specifically crafted to ensure scarcity and control over the resource the blockchain ledger tracks. The problem is that most decentralized applications do not need a notion of scarcity. The whole damned point of P2P is to punish artificial scarcity. If I want to communicate to someone else over a decentralized network, I don't need a Sybil-resistant ledger to do so. I just need a private/public key pair and some means to match interested recipients and senders. Same with a lot of other decentralized use cases, which also don't need to be able to track scarce assets.