Currently there are only a handful of people who can carry on the development of Bitcoin. Introducing new core developers requires highly skilled engineers to first get interested in Bitcoin and then invest significant time to gain experience and catch up to the knowledge pool. You can re-arrange the hierarchy of current Bitcoin Core developers a little bit, but you cannot expect a completely new team to take over anytime soon.
We need new engineers to get involved and need to better document current knowledge. Making it easier for engineers to get involved is important, but in the short run there is no replacement for Core developers. Rolling Out Networking Protocols Takes Time:
Most disruptive technologies went through periods of heated debates.
Moreover, upgrading networking protocols takes longer because you need to update already deployed infrastructure that is interlinked. TCP's basic operation has not changed significantly since the first specification (1974) and the v4 specification (1981). Updates to TCP, e.g., TCP Vegas
, take years before they are widely deployed or incorporated in the Linux kernel.
Compared to other revolutionary open-source technologies, the rate at which Bitcoin Core is evolving is impressive. It's a success story. Reliability, Security, and Inclusion is More Important Than Bandwidth:
I'm surprised by how big an issue the blocksize debate has become when the current bandwidth is clearly not throttling down usage in any significant way. We, at Onename, were sending 50–100 blockchain ID transactions per block last week (~9,000 total
) and didn't hit bandwidth limits or spike fees.