> Except I'm not assuming it's wrong because it's unpopular. Read the original comment, I clearly stated why it's wrong. Except you clearly are. The only other

> Except I'm not assuming it's wrong because it's unpopular. Read the original comment, I clearly stated why it's wrong. Except you clearly are. The only other reason stated in the original post seems to be "because it's similar to what the hardware does", which in my opinion is completely irrelevant - how does that in any way change how useful it is to program with? > Also, please show me one successful software package (and by successful, I mean largely consumed by consumers and a product leader) that does not use looping techniques. Must functional programming languages have no loop construct or using loops is heavily discouraged. > Like all technical decisions, they are made by using the most correct and appropriate choice. I don't believe that you're naive enough to think that one decision is correct in all scenarios, or that programming paradigms cannot evolve over time. > Which is why the industry has been using pre and post condition loops since the beginning. Congrats, we're back to "it's popular so it's good".