Honestly I don't think the problem is going to get fixed preemptively, I think it's going to get fixed reactively. Essentially somewhere along the line Hive scaling is going to fail spectacularly. It will be at this point that all the devs will wonder what went wrong and try to fix it, and Condenser combined with our extremely inefficient API will be pointed out to the entire network as the root cause.
I like databases, but most people find database work boring, so they want to work on more exciting projects. Combine that with the fact that no one wants to work without getting paid, and Condenser development will remain stagnant until it is deemed to be a high priority issue due to systemic failure.
Hopefully it doesn't come to that and we get some more devs who enjoy database work, but I'm not going to hold my breath on that front. In the words of Andreas Antonopoulos, our success will be measured in our ability to fail to scale gracefully over time, just like the Internet itself.
RE: POB Part 4: Graphene vs Condenser + Databases