I was using the term develop more broadly than just code development (but some ongoing code development is needed too)
You seem to have a viewpoint that spending should only be programmatically constrained and close to proportional to market cap, and this contrasts rather starkly with the structure of the DHF, which is organized around the notion that stakeholders can subjectively decide what to spend and when to spend it based on perceived merit and perceived value in developing (and using the term broadly) the platform and ecosystem, with only lax programmatic limits. Once again, I would say that if you don't like DHF having loose limits on spending, the direct recourse is to vote return, not vote other proposals, and advocate for other stakeholders to do the same. I've mildly advocated along those lines myself. And, again, if other stakeholders outvote us, then that's how it goes. Likewise for a hard fork, but that's likely to be an even heavier lift.
RE: How to Reduce Hive's Inflation Problem - Our New DHF Proposal Voting Criteria, HBD APR, and a Proposed Value Plan S.O.P