Your argument here isn’t very clear. Could you try to make each step in your reasoning explicit?
Uh, no. You specifically asked for a succinct explanation, and I gave you that, along with a link to a good, meaty article. If you suppose Miller’s just grinding an axe with that, I’d be a fool to spend any more time on this with you – I’m not gonna do better than he does, here. Perhaps many of the concepts and terms he’s using are just unclear, and more background reading on the subject would help?
I’ve read part of Miller’s article and so far it’s certainly clear that he’s grinding an axe. I’ll continue, however. In the meantime, what about my other question? Do you think rossum’s example of an IC system - a bridge made of a log resting on two stones - is a good one? Why or why not?
Rossum’s example was awesome. I’d like to use it myself, going forward, because it’s very simple, yet very clean in demonstrating the princple. And, you can illustrate it in simple ASCII characters (that makes it awesome).
The function of the system is “crossing the creek”. Initially, a set of stones gets put out, one by one. At first, the walker can only get a step or two out into the creek, not even across it. But with each successive stone, more progress, until the creek can be crossed from bank to bank. But a log placed (or fallen) in one step makes some/many of the stones superfluous. They can be washed downstream, or other wise removed, and the creek can still be crossed.
An ID-IC advocate would say “Irreducible Complexity”! The stones in the middle are gone, after all, and removing that key log would leave the subject nowhere! And that’s true, but it’s just painfully brittle in its thinking. The stones stepping across the creek were incremental, and useful at each addition, but became superfluous, unneeded, later as another incremental step provided a better solution. The obsolete parts can wither, or otherwise disappear, but the step-wise history remains just that – step-wise, incremental, non-magical.
So yeah, thumbs up to rossum on that one. That’s high quality – pedagogically powerful, and true to the concept.
I didn’t like the monolith/arch example because a key in this is the component/step-wise nature of the development path, which “erosion” seems to leave out. The stones and log example preserves this nicely. And I can relate it in ASCII, to boot. Cool.
-TS