The great thing about DASH is that it's the topic on everyone's minds.
The takeaway from that exchange is a general state of cluelessness and ZX Spectrum programming mentality.
There's nothing incorrect in what they're saying (as far as I know) - it's just the total absence of perspective on competing priorities.
I don't know if either of them spent the last 30 years of their life building professional software systems or not, but how Evan's approaching it is absolutely consistent with an optimal strategy IF you're continually targeting protocol level revisions/improvements in a deployed technology.
He's alternating between development and deployment priorities. Thats what the spork is - an airlock for deployment.
Who cares if it creates a temporary window of control - all these currencies are in an embryonic state. If any of them achieve anything near their development objectives then that will be the least of anybody's worries. Anyway, the worst he can do is revert to the previously adopted protocol logic.