Actually, from all the analysis it seems:
- If you have shallow loops - feel free to use continue iff it improves readability (also, there may be some performance gains?).
- If you have deep nested loops (which means you already have a hairball to untangle when you re-factor) avoiding continue may prove to be beneficial from a code reliability standpoint.
In defense of Douglas Crokford, I feel that his recommendations tend to lean towards defensive programming, which, in all honesty seems like a good approach for 'idiot-proofing' the code in the enterprise.
