What is the point of the no-continue rule?

The official ESLint docs say “When used incorrectly it makes code less testable, less readable and less maintainable.”

Does Airbnb agree with the above reasoning? If so, can you give an example of how continue makes code less testable and less maintainable?

(I’m not arguing against it btw, just want to understand why.)

[ljharb]

continue, like break, is GOTO. There are countless articles on the internet about GOTO being harmful.

In addition, this style guide discourages loops, which are the only places you’d need continue or break.

[SelaO]

@MegaArman Loops are still useful in 2018 in many non trivial cases and will stay useful even in 2118, you can’t do everything with map, reduce, filter.

See the example I gave above and tell me how continue is “bouncing around” like goto is.

but imagine working on a large codebase with lots of loops and if statements with continues scattered about

That’s an invalid statement, if the code already become such a mess, then not having continue and breaks won’t help you, loops shouldn’t be huge, just like functions shouldn’t be huge. Banning basic coding concepts isn’t a magic tool to make code more readable and maintainable, and oftenly can make the code even less maintainable (like more complex stopping conditions in no continue loops)