[mrkeen]

> The entire point is to change things

We've other 'entire points' along the way.

Allocation and freeing of memory are fundamental to computing. We don't do malloc and free any more.

Control-flow (selecting which instruction to follow next) is also fundamental. We don't to goto anymore.

[taeric]

I'm not entirely clear what you mean. I can easily see malloc/free in the realm of "incidental complexity." Many of the abstractions in process descriptions are absolutely not incidental, though?

Control-flow is an awkward choice there, as goto is not necessarily fundamental for how control-flow is run for a lot of code. And I have absolutely used labeled break/continue in Java before for a control loop that ran great until people tried to refactor to use more indirect control.

I also think it is interesting as I greatly prefer code where you can do basic left/right and top/down reading to know what is intended by the code.

At any rate, my original intent was to discuss code that is controlling something works really well if you embrace a metaphor for the code you are in.