|
When writing code for a blockchain today, even on an Ethereum L2, you're in a very resource-constrained environment where you end up using bitpacking tricks and the like. That's how it was for early computers, too, of course — they may serve as a better analogy. Programmable computers have taken decades to develop, beginning in ~1950, and I expect that decentralized computation will follow a similar path. There simply are numerous hard problems to solve to make this all work at greater scale. In a healthy ecosystem like Ethereum's, there are frequent research discoveries (discovery of the concept of data availability, the application of BLS signature aggregation, proposer-builder separation, zkevm, data availability sampling, ...). The software engineering effort required to implement such research is colossal as well. Eventually we'll even see e.g. specialized hardware for efficiently producing or verifying zero-knowledge proofs. It would be easy to look at the very early computers, which were perhaps not all that useful, and shrug — but that take wouldn't have extended well into the future as the technology scaled. |
Ok, so there is a massive amount of effort to be put forth to get something out of this, and even then it is still kind of up in the air what that "something" actually is.
Would it not be prudent to have at least some sort of roughly sketched map of what all this effort is supposed to bring about? other than Lambos...
Or maybe ask if we would be better served if all that effort was put forth in some other direction? Man hours are not a limitless resource.