Wouldn't separate experiments : one for bigger blocks and another for alternative solutions to transaction latency whilst maintaining decentralization, make us all winners once it becomes clear which approach could best be leveraged to defeat Bitcoin's real enemies?
I won't claim to have looked at the problem from every angle, so please highlight any glaring problems with a hard fork I may be missing.
This is exactly what i have been thinking all day, and to be honest if any off my friends and family ask about this i will be explaining that bitcoin is open source and this sort of thing is a feature of open source software, its a feature not a bug......