loops

That's been my experience too, not just of Duff's device but in general with trying to unroll loops.

Second, arrays are rather simple data structures, but ones where you often care about performance--small tight loops are common.

Can you say what kind of stuff and in what kinds of situations you unroll loops.

Move up to conditionals, loops, add in methods later in a sort of procedural fashion.

It just took a few decades of the natural self-reinforcing loops of capital to highlight the inequality that was already there.

You can teach loops and draw graphics in just a few lines of code: What!

It had functions, loops, block ifs, and all the other staples of structured programming.

You can teach loops and draw graphics in just a few lines of code: import turtle turtle.setup() turtle.forward(100) turtle.turn(90) turtle.forward(100) And so on.

It didn't require line numbers and had all the necessary tools like functions and procedures, for and while loops, blocks, user-defined types, etc...

And teaching loops without intermediate variables is much easier.

And it's true, as @pflanze's comment correctly points out and I think you're getting at, that loops aren't sufficient – but gotos are.

I generally start by introducing three fundamental concepts: variables, conditionals, and loops.

In these cases, the compiler will usually "do the right thing" when optimizing loops like this, where it sometimes can't do that optimization for unsigned loop variables.

"Single versions of truth" ( single UI, single UX, single algorithms ) for everybody don't help this, they reinforce the feedback loops and amplify these harmonics.

One such I remember reading about recently is Fruity Loops, one of the most popular (though entry level) DAWs.

Loops are not the only use case for TCO.