I think this point will help get clarity. Why won’t a common design provide branches with better than chance support?
Because there is no reason to. You can’t come up with a reason. No ID/creationist can come up with a reason. There are millions and millions of reasons why a designer would not use a nested hierarchy.
Wrong question. A better question would be to ask “Why would it?”
You’re just asking, with different phrasing, why common design would not produce a nested hierarchy, and the answer is simply that we have no reason to think it would, yet we have good reason to suppose that common descent does produce a nested hierarchy. So we’re back to this: what is the explanation for the nested hierarchy of deer species?
Any process that reduces chance events will pass your test. Both common design and common descent reduce chance events. If you read between the lines this is something Winstons paper demonstrates.
The nested hierarchy or tree is not a differentiator here.
Incoherent again. This is not a topic you understand. Then again, it’s central to my profession. Could it be that I understand it better than you do?
Ewert says just the opposite.
Of course you understand this better then I do but that does not mean your test can eliminate common design.
The point of failure of your test is not robust enough to differentiate common design and common descent. It is only robust enough to differentiate common design or common descent from chance.
But it does mean that you are not competent to decide that it can or can’t, and it means that you have no idea what you’re talking about. Wouldn’t you say? (Also: thAn!!)
More incoherence, but I’ll see what I can do with it. It’s true that it’s impossible to test for common design without having some kind of expectation for what common design would produce. My contention is that nested hierarchy is not such an expectation. If you disagree, you need to explain why it would be an expectation. Failing that explanation, seeing nested hierarchy leads to a conclusion of common descent.
And once again, since you seem unwilling to see this: mere degrees of similarity do not produce nested hierarchy. This is one of the most basic understandings of phylogenetics, and that can’t be stressed enough.
Parsimony eliminates design.
It’s the same way we eliminate God planting fingerprints at a crime scene as an explanation for forensic evidence.
My expectation that design would produce a nested hierarchy is because it will pass your test (for a nested hierarchy) as design reduces random chance events.
Winston showed how software programs that share code will generate a tree diagram.
Human designs reduce random chance events and they don’t fall into a nested hierarchy. Your claims make absolutely no sense. You can reduce random chance events and still not have a nested hierarchy.
He showed just the opposite.
Here is the tree diagram for software modules.
Look at figure 6. That’s a web, not a tree.
More incoherence. Reduction of random chance events has absolutely nothing to do with producing a nested hierarchy.
It does in conjunction with building unique living animals that share common cellular components. I will try to be more explicit going forward.
Good. Also try to be more coherent as well. So far, neither.
The ones that fixed weren’t deleterious? You know, like in mice.
That would increase the strength of selection in the mouse population. Deleterious mutations should have a harder time rising to higher frequency in mouse populations compared to deer populations.
Species can share common cellular components and not fall into a nested hierarchy. You still don’t seem to understand what a nested hierarchy is.
Bill, just for laughs, please define “nested hierarchy” with no reference whatsoever to biology.