I agree with the premise of the article but there's more to consider than just the blockchain. There are three issues that must be dealt with when trying to make it easy for developers to create decentralised systems that can withstand the test of time. There are a number of (open-source) things I'm working on that could help so I'll describe in terms of the problems they're solving.
First is the issue of how one creates, deploys and manages the whole lifetime of an application. The current stacks are not up to the task given the huge complexity, footprints and vulnerabilities we see. All the tools we currently see are stopgaps that attempt to paper over the cracks. This will become even more important (and visible) as the Internet of things becomes a reality. IMHO this is where unikernels such as Mirage OS can be very impactful [1].
Second is the issue of how data is synced and pushed around. As indicated in the article, the blockchain is not appropriate for this. Bit-torrent may provide some of the answer but not all of it. We needs systems that can track provenance that can be composed in the way most appropriate for a given application. The Irmin datastore, which is based on the principles of Git, is one approach to this [2].
Third is the dual problem of identity and how to form secure end-to-end connections over the modern Internet (with all the middleboxes and NATs we now have). This is clearly something all the central providers want to control by being your One True Identity - but as we already know from the pseudonym problems, humans are not that simple. A nascent project called Signpost aims to tackle this [3].
One of the use-cases I'm working towards is to make it trivially simple for users to run their own core infrastructure of Mail, Contacts and Calendars [4]. Building things on top of this infrastructure then becomes more compelling and it's just as applicable to business as it is to individuals.
Even though I've listed the tools that I think will alleviate the issues, the fact remains that all these problems needs to resolved somehow - otherwise we'll be back to centralised systems regardless. In addition, I've only mentioned the technical challenges — the business model challenges are another thing entirely.
[1] http://openmirage.org/wiki/overview-of-mirage
[2] http://openmirage.org/blog/introducing-irmin
[3] http://nymote.org/docs/2013-foci-signposts.pdf
[4] http://nymote.org/blog/2013/introducing-nymote/