STEEM's PoB Not Designed For Lengthy dApp Development Or Large Initial Capitalization

From The Follow-Up Steemit Blog Today

While there's probably much more to be concerned with as far as HF 21 goes, the following paragraph I made an image of caught my attention:

Interesting enough, I read something similar to this within the first three or so months on STEEM, but when I went looking for it more recently I couldn't find it. For me, the most relevant of this paragraph:

Steem’s Proof-of-Brain algorithm was not designed to incentivize projects with long gestation periods and which require significant upfront capital expenditures.

That sentence is what has irked me about the way dApps end up on STEEM. Instead of doing what STEEM Monsters and a few others have done—creating a business model where actual STEEM/Fiat is required to play/purchase/grow stake, thus generating actual revenue for the dApp—instead we have a myriad of dApps all doing what users are doing, at least those who curate, and that's basically upvoting user content in hopes of making enough SP to pay for current and future development.

Which means dApps are in a constant state of powering down without some other funding source, and they might manage to keep up with expenses only if they have hundreds of thousands to millions of delegated STEEM, which is the case for quite a few dApps.

Again, this has all been going on for quite some time despite the fact that:

Steem’s Proof-of-Brain algorithm was not designed to incentivize projects with long gestation periods and which require significant upfront capital expenditures.

Questions come to mind. I could enumerate them, but I don't know if there's really any point. Other than, in a rush to bring on dApps, or some other reason, instead of going straight for a worker proposal like the STEEM Proposal System, we got workarounds and misuse of STEEM's proof of brain. By misuse, I mean, against it's design.

It's these kinds of things that make me wonder what's really going on. It doesn't have to be anything sinister either. It can be something as simple as misplaced priorities and we get to the same place. It didn't take long for the SPS to get coded. If it were the only thing going into the upcoming hard fork, we'd probably have HF 21 before now. So, in the end it's a relatively easy thing, when there's knowledge and wherewithal to see it come to pass.

Truthfully, I don't really know why I'm bringing this up. I do think people should be aware of this and what's been going on because of it. I don't think it's something that should be glossed over and forgotten, simply because there are other things more pressing. I think it does need to be remembered, and recalled to mind as STEEM rolls on, that we don't continue to just let things that the system wasn't designed to do to continue.

No matter who's helping it to happen.

The problem is actually doing that. Knowing that something isn't designed to do what people are using it for, and then stopping the practice has been virtually impossible from what I can tell because we can't get to any consensus but endlessly chase our tails around in a circle because of this reason or that, while some cheer it or wave it off as decentralization at work.

My guess is, the majority of us just thought that this was the way it was supposed to be, that dApps used proof-of-brain to get off the ground, even if it didn't appear to work very well, and even though quite a few dApps have disappeared overtime, to which some of it could be for lack of necessary funding.

Maybe I'm trying to say, I like the idea of the SPS, and of all the things happening in the new hard fork, it's the one thing I actually have some hope for. I'm just wondering, like I've wondered a dozen times before, why wasn't this one of the first things to be done?

I know, I know. It's now being done, so take a deep breath. As I said. I'm glad, after I've had time to evaluate it, that something is happening. Whether it works or not, just like everything else on or off STEEM, is yet to be seen.

What will be interesting to see is how much the current dApps, and new ones to come, use it as a way to finally improve their offerings, or get a foothold on STEEM. Meaning, there could be a boatload of dApp improvements to wade through for users, in addition to whatever community driven improvements may arise. Or developer dream projects.