Those two quotes overlap but they don't quite coincide if you notice. In mikes it would appear "deliberately cripple" means not raise the limit from 1 MB ever. garizk's on the other hand said it can scale even with the limit.......... correct me if I'm wrong plz
There is also a thread, maybe even this one, that starts with the premise that raising the limit before the optimisations are in place pretty much just invites not bothering with the optimisation, since the limit can just be skyrocketed, or eliminated, or increase over and over again (any time someone otherwise might have to actually materialise these vapourware optimisations even maybe...)
Which makes maybe a middle ground: deliberately crippled by the vaporware optimisation creators' or inventors' failure to materialise the optimisations.
Once optimal use is made of the size already provided, more size might reasonably be made available. While the size already provided is being wastefully wasted, throwing good size after bad doesn't seem like a good way to motivate materialisation of that vapourware.
The worst thing that can happen for Bitcoin is for scalability solutions to exist, but not be adopted for political reasons.
If they weren't vapourware, they would probably have been adopted by now.
Increasing the size prematurely isn't scalability, its actual scaling. Heck even when it is time to do it (when it is no longer premature) it still will be actual scaling, not mere scalability. Get the difference? Scaling (actually increasing the size) awaits scalability (the mythical or vaporous or simply not quite yet ready to be merged-in optimsations).
-MarkM-