I've got to say I'm a bit confused as well.
My understanding is that the goal behind EOS is to create a blockchain with the speed and design to be able to handle 10s of thousands of transactions/second, allowing dApp developers to create scalable dApps.
Now this post talks about how developers will likely only use a small portion of the memory they've purchased through ownership of the EOS tokens, because otherwise the cost of the memory would be too expensive compared to a centralized application.
How does this benefit dApp developers?
Decentralized app developers will always have to pay the price for decentralization in order to gain the benefits of decentralization. The purpose of EOS.IO software is to reduce the cost of decentralization.
The most you can reduce the cost is to lower it to the actual physical resources (redundant nodes) the dAPPs are using.
The purpose of this article is to address concerns that the monetary demand for tokens will artificially over-price the memory. A new algorithm counterbalances monetary and industrial (dApp developer) demand for tokens/memory.
Ok, that makes more sense. Thanks for that clarification.
Very impressive. This post allows us to actually grasp the decentralization challenges for a Platform like EOS. Every problem has to be solved in a new perspective. It is truly amazing to read your posts @dan. Thanks to take the time to educate us on these subjects.