Field length in network protocols matters; you can extend a field, but reducing it at a later stage after network participants (like whirlpool) have begun to rely on the field length is considered a backwards breaking change.
Discussion
Luke has answered this elsewhere. It's unfortunate his positions on specific topics aren't indexed somewhere that he can just reference by code.
His position is that from inception the field was standardized at 40 bytes, intentionally to limit spam. So reliance on and design around an expanded field size is a mistake on their end, for non-conforming to the "spec".
Things like this in protocols tend to be worked out by representative bodies and industry boards such as w3c, iso, among others over time. These standards also tend to compete for adoption.
Bitcoin being money, a new project and a philosophical or religious paradigm shift for participants, with enourmous social consequences, it will take a while to smooth out the standard.
That's a falsehood Seagull, and you can find it out yourself by looking at the bitcoin-dev mailing list and the bitcoin git repo.
80 bytes was the intended OP_RETURN this whole time, it's just that Core decided to incrementally roll it our for safety reasons. After 9 months at 40 bytes, with nothing breaking, they concluded at 80 bytes, which it's been that way for a decade now.
Luke is lying.
Cypherpunks write code.
