tag:blogger.com,1999:blog-3855268335402896473.post1425192598537852636..comments2024-01-23T02:32:28.567-08:00Comments on Darwin's God: Amazing Preparations for Cell DivisionUnknownnoreply@blogger.comBlogger46125tag:blogger.com,1999:blog-3855268335402896473.post-55122836618051925202009-10-20T23:25:52.958-07:002009-10-20T23:25:52.958-07:00Brian: "I think I owe you an apology."
...Brian: "I think I owe you an apology."<br /><br />I accept! I appreciate your explanation later as well. The only reason I keep replying is that I can tell you would like to be fair, even though we disagree.<br /><br />I don't take your rejection or disrespect of my points personally at all, don't worry. That's my personal first tenant of rationalism. Also, complexity doesn't imply design :D.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-69539749626643325492009-10-20T11:18:39.869-07:002009-10-20T11:18:39.869-07:00Shirakawasuna:
I think I owe you an apology.
At ...Shirakawasuna:<br /><br />I think I owe you an apology.<br /><br />At your urging, I re-read the thread again and I now see what you mean about the altered quote. I used your real quote in one reply --<br /><br />"I said it directly: complexity does not imply design."<br /><br />and then I used a paraphrase<br /><br />"complexity never implies design"<br /><br />a little later on, without catching the subtle difference in meaning which you insist upon.<br /><br />Now the significance of your "double quote", "lie of a quote", and other comments becomes clear, and my reaction was unjustified.<br /><br />We could quibble about how significant the difference is between "does not" and "never" but I do now see your point, and I am sorry for the muddle which resulted from my substitution. I did not mean to put words in your mouth.<br /><br />That said, I still think most everything else you have written is vague, false, and/or illogical, if not self-refuting. Nothing personal! :-)CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-48430617842937607442009-10-17T13:51:40.951-07:002009-10-17T13:51:40.951-07:00Correction: rather than not following, your argume...Correction: rather than not following, your argument (to which you want me to agree or disagree) assumes a false premise.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-78179809655355563362009-10-17T13:48:56.664-07:002009-10-17T13:48:56.664-07:00"First, you took pains to "directly"..."First, you took pains to "directly" state your illogical position. Then, you "clarified" by making a completely different statement, and asserting that the two statements were consistent with each other. They were not."<br /><br />Bull. Why is it that every time you make a reference to what I've said, you manage to get it wrong? This is the internet, just *read*, Brian.<br /><br />When I said 'directly': "Your intended summary of my point is inaccurate. I said it directly: complexity does not imply design. There are very good alternative hypotheses, mechanistic ones, that just happen to be testable (and have been tested)."<br /><br />When it became clear that you were misinterpreting what I said (and getting confused about the fallacy of equivocation), clarification was necessary. Remember my computers -> dolphins example? Having said that comuters are not derived from dolphins, wouldn't expect someone to ask for a disproof that dolphins are not made of computers: it's a statement derived from induction. I would also not say, "computers are never made of dolphins", because I understand the implications of the word 'never'.<br /><br />So, how was I inconsistent, Brian? You have a terrible track record of knowing what I've said so I expect actual quotes and demonstrated inconsistency rather than another inaccurate summary and implication.<br /><br />"Attempts to clarify your new statements were met with Humpty Dumpty logic:"<br /><br />Nonsense, I told you precisely what I meant and you at no point addressed it. You happily continued under your misapprehensions, acting oblivious to the clarification. You're doing it now, in fact.<br /><br />I'll note that this is *still* true: "Nonsense, you accused me of it and I explained my meaning. I still use the same phrase I used originally, now that I've explained what I mean."<br /><br />I will still gladly say that complexity does not imply design. If you don't know what I mean by that, you haven't been paying attention the last 12 times I've explained it.<br /><br />"As to the last half of your reply, you imply that I am making a nonsense statement."<br /><br />When? Did you confuse a silly analogy for implying that you have a nonsense statement?<br /><br />"I am not. I am making propositional statements, and asking you to agree or disagree."<br /><br />And your logic did not follow. I explained my meaning and what it means to reject your "quote". Perhaps I was not direct enough in explaining what it means to have a provisional position, that (for the 73rd time) I have never seen a complexity argument with follows and that that is what "complexity does not imply design" means. Having never seen one which follows does not mean one cannot exist, so I reject the "never" claim. Having never seen one also does not imply that one does indeed exist. You are taking my position as if it's based, in totality, in deduction, when it is also an inductive statement. I hate to sound mean here, but I would have thought that would be obvious having said again and again and again and again that my position is that I've never seen one which follows. You seemed to understand what that meant before, as you started coming up with examples you thought worked.<br /><br />"I am attempting to ascertain whether you accept the basic principles of logic -- it is not clear to me that you do."<br /><br />Yet it is your misunderstanding that is at question, here. Perhaps, *again*, you should read what I say more carefully, dare I say, for comprehension?<br /><br />"I have acknowledged your reply repeatedly, but I do not accept it, because it does not comport with logic or the facts."<br /><br />Then demonstrate it. Your exercise so far seems, to me, to be to repeat your initial misunderstandings and pretend that clarification is equivalent to a moving goalpost.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-85014633926301667032009-10-17T06:50:15.841-07:002009-10-17T06:50:15.841-07:00Shirakawasuna
First, you took pains to "dire...Shirakawasuna<br /><br />First, you took pains to "directly" state your illogical position. Then, you "clarified" by making a completely different statement, and asserting that the two statements were consistent with each other. They were not.<br /><br />Attempts to clarify your new statements were met with Humpty Dumpty logic:<br /><br />`When I use a word,' Humpty Dumpty said, in rather a scornful tone, `it means just what I choose it to mean -- neither more nor less.' <br /><br />Read your Carroll if my meaning is not clear.<br /><br />As to the last half of your reply, you imply that I am making a nonsense statement. I am not. I am making propositional statements, and asking you to agree or disagree. I am attempting to ascertain whether you accept the basic principles of logic -- it is not clear to me that you do.<br /><br />I have acknowledged your reply repeatedly, but I do not accept it, because it does not comport with logic or the facts.CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-60805450000660590012009-10-13T18:13:21.280-07:002009-10-13T18:13:21.280-07:00typo: "Now, I actually would claim that"...typo: "Now, I actually would claim that" -> "Now, I actually wouldn't claim that"Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-8017437126011980112009-10-13T18:11:54.144-07:002009-10-13T18:11:54.144-07:00"This whole thing has gotten far too complica..."This whole thing has gotten far too complicated."<br /><br />I agree. I stand by my allegation that you ignore my clarifications and stick to your original opinions, despite said clarifications. I wouldn't be surprised if when I look back at what was written, a large amount of the confusion is due solely to that.<br /><br />"You accused Dr. Hunter of fallacy, and supported your point with a fallacious statement."<br /><br />First clause yes, second clause disputed and argued, with a poor performance on your side (see the complaint above).<br /><br />"I called you on it, and you backed off the statement."<br /><br />Nonsense, you accused me of it and I explained my meaning. I still use the same phrase I used originally, now that I've explained what I mean.<br /><br />"I don't know why there had to be so much hub-bub about it. There is no shame in backing off of an illogical statement."<br /><br />Of course there isn't. Your insinuation that the problem is a sense of shame is speculation directed at my person and is particularly silly considering that I keep telling you over and over and over how I think you're wrong.<br /><br />"If you reject the statement:<br /><br />"complexity never implies design"<br /><br />then it logically follows that you must accept the statement:<br /><br />"complexity sometimes implies design".<br /><br />Right?"<br /><br />If you completely ignore everything I've told you and focus only on the fact that I called your quote a lie of a quote (which it still is, I didn't say it), then yes you would be right.<br /><br />If you were go peruse what I have actually said, though, you would find that I say your "quote" implies a level of certainty I do not claim, i.e. that I can disprove the entire notion rather than pointing out that I've never seen any version which follows.<br /><br />Let's take an example: "Apples never implies leprechauns". Now, I actually would claim that. It implies that I can disprove such a notion or otherwise is an argument from ignorance/lack of imagination (implicit). I would say, however, that I have seen no such argument which follows, certainly not one where the apples are actually the fruit you're thinking of, leprechauns are the actual mythical creatures referenced, and they are proven by the mere existence of apples.<br /><br />How many times do I need to repeat this reply until you acknowledge its existence? It seems like an awful lot of work just to force you to follow my points.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-24174573038979453372009-10-13T05:43:18.322-07:002009-10-13T05:43:18.322-07:00Shirakawasuna:
I think we have established that t...Shirakawasuna:<br /><br />I think we have established that there was never any "lie of a quote." <br /><br />Again, Shirakawasuna said...<br /><br />"I said it directly: complexity does not imply design."<br /><br />This whole thing has gotten far too complicated. You accused Dr. Hunter of fallacy, and supported your point with a fallacious statement. I called you on it, and you backed off the statement. I don't know why there had to be so much hub-bub about it. There is no shame in backing off of an illogical statement.<br /><br />Now, here is the really interesting point to me:<br /><br />If you reject the statement:<br /><br />"complexity never implies design"<br /><br />then it logically follows that you must accept the statement:<br /><br />"complexity sometimes implies design".<br /><br />Right?CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-80010930769725725592009-10-12T11:09:12.749-07:002009-10-12T11:09:12.749-07:00Aha, I have finally figured out the miscommunicati...Aha, I have finally figured out the miscommunication, Brian. <br /><br />I was referring to this: ""complexity never implies design"<br /><br />I replied first with this:<br /><br />"When did I say that, Brian? Why use double quotes if you're paraphrasing? When did you ask something that appears nowhere in this thread? No, my point is that I've never seen a design from complexity argument which follows, AKA complexity does not imply design. Using the word 'never' can imply a level of certainty restricted to math and logic."<br /><br />Then after some more commentary, I moved on to your next sentence:<br /><br />"It is obviously an ambiguous statement, just as "complexity implies design" is an ambiguous statement. Both statements require further clarification to be meaningful, i.e. "complexity" must be further defined. "<br /><br />And then I said it was a good thing I didn't say your lie of a quote (i.e. "[...] never[...]"). I had already clarified what I meant severeal times by then just to have you resimplifying it and putting words in my mouth.<br /><br />If that isn't the problem, then I have no idea what to tell you. I never said, "complexity never implies design", I said repeatedly that complexity doesn't imply design and when it was misunderstood, what that meant.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-91361923134713174212009-10-12T09:34:40.767-07:002009-10-12T09:34:40.767-07:00Shirakawasuna said... (earlier)
"Then you (B...Shirakawasuna said... (earlier)<br /><br />"Then you (Brian) bring up "quotes" of myself which exist no place in this thread (nor elsewhere)."<br /><br />Shirakawasuna said... (just now, faced with undeniable evidence)<br /><br />"Yup, Post #8, my second post. I made the mistake of using common language, so I had to clarify later exactly what was meant."<br /><br />Thanks for clarifying that I did not make up the quote. Just wanted to set that straight.<br /><br />Now, the question of why you claimed I made it up is still unsettled. If you made a simple mistake, why not just confess it?CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-16108234826813432332009-10-12T06:18:06.686-07:002009-10-12T06:18:06.686-07:00Yup, Post #8, my second post. I made the mistake ...Yup, Post #8, my second post. I made the mistake of using common language, so I had to clarify later exactly what was meant. I did it many times with no acknowledgment (and you kept making the same mistake). After all that, you come back and rephrase the statement in stronger words.<br /><br />"In case you're still laboring under the impression that your "quote" captures my point, I will say yet again (why so many times?) that I have never seen a complexity argument which follows. They aren't cogent. I do not use the word 'never' because it implies a level of certainty I do not claim. It would place the burdon of proof on me to disprove complexity -> design, something I don't claim. Do I have to explain this over and over or will you listen this time?"Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-68359751232173081222009-10-11T21:51:22.328-07:002009-10-11T21:51:22.328-07:00Shirakawasuna said...
"I said it directly: c...Shirakawasuna said...<br /><br />"I said it directly: complexity does not imply design."<br /><br />Post #8, Paragraph #2, Sentence #2.CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-59861834049133056392009-10-11T14:29:50.699-07:002009-10-11T14:29:50.699-07:00Brian, you've repeatedly misunderstood what I&...Brian, you've repeatedly misunderstood what I've been saying. Then you bring up "quotes" of myself which exist no place in this thread (nor elsewhere). That's disingenuous and I called them lies, but I never *called* you a liar. Why not admit your mistake, call them lies, then move on? It's hardly civil to make up quotes and stick them into someone else's mouth, yet you find it so terrible that I call the result a lie?<br /><br />Ah, of course. You don't think you were wrong.<br /><br />You say I have a "sea of garbled and vague assertions" and have identified something clear, yet you make it up and pretend it's a quote? No. What you claimed I said was: "complexity never implies design". I have been very, very clear on what I mean here and if you have a complaint, address it against what I actually said. Quote me. You managed to do it now that you're indignant.<br /><br />In case you're still laboring under the impression that your "quote" captures my point, I will say yet again (why so many times?) that I have never seen a complexity argument which follows. They aren't cogent. I do not use the word 'never' because it implies a level of certainty I do not claim. It would place the burdon of proof on me to disprove complexity -> design, something I don't claim. Do I have to explain this over and over or will you listen this time?Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-29837195326608811572009-10-10T11:33:35.882-07:002009-10-10T11:33:35.882-07:00Shirakawasuna:
I offered you the last word of the...Shirakawasuna:<br /><br />I offered you the last word of the debate so we could end on civil terms, not so you could dismiss my words as those of a liar.<br /><br />Regarding my "lie of a quote", as you call it:<br />"complexity never implies design"<br /><br />You now ask:<br />"When did I say that, Brian?"<br /><br />Post #8, paragraph 1-2 (in context):<br /><br />****************<br />Brian, I was intentionally vague with my use of the word complexity. I didn't make any equivocation, it's still a fallacious complexity -> design argument. If you're hung up on me calling this stuff sloppy, don't be. It's a way do describe how you'd expect complicated systems, even with great specificity, to have a bunch of interacting parts.<br /><br />Your intended summary of my point is inaccurate. >>>I said it directly: complexity does not imply design.<<< There are very good alternative hypotheses, mechanistic ones, that just happen to be testable (and have been tested)."<br />****************<br /><br />In a sea of garbled and vague assertions, this is one of the few clear statements you made, which is why I remarked on it. Unfortunately, it appears that you can't even remain true to your clearest, most "direct" statements. <br /><br />Shirakawasuna, be honest with yourself. Did you just tell a lie, and then call me a liar? Why would you do that?CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-80458365377442490132009-10-10T10:14:23.730-07:002009-10-10T10:14:23.730-07:00"I attempted to craft a sentence which I felt..."I attempted to craft a sentence which I felt restated your position exactly, but you rejected that as well, although I don't understand your objections to my attempt."<br /><br />I rejected it because it revealed an easily-corrected misunderstanding: you mixed up to what noun the messy was applying. You keep going on about my cells aren't messy. I would argue that they possess elements which are quite messy and some which are beautifully elegant, but it's another topic from what I said originally and you continue to be confused about. I have clarified this. If the clarification is lacking then you need to ask specific questions rather than restating the misapprehension, as it often seems you really haven't read what I said very carefully. Every time you make those mistakes, I explain how it's wrong or push you towards reading my clarification. Every time, you restate your original erroneous idea without addressing my specific replies.<br /><br />"I thought we could proceed with this discussion, but I don't see it going anywhere. I made a good faith attempt to explain one last time, but it seems to be beyond my powers to make you understand."<br /><br />I'm not the one with demonstrated problems understanding the other person. Whenever I make a mistake concerning your meaning, go ahead and correct me, I'm game. There's a difference between agreeing with you and understanding what you're saying and I believe you've confused the two.<br /><br />"It appears to me that you wish to hold to a very tightly scripted rejection of design arguments, and resist further admissions which might be "damaging to your case.""<br /><br />I haven't a clue what you're talking about, I reject design arguments because they don't follow: I've never seen one successfully even approach cogency. You haven't even listed the best ones, which still make serious errors. What about my statements there are equivocal? I'll remind you that I've explained what equivocation is twice, without your reply.<br /><br />So, what admissions are you suspecting? It's hilarious that you think I'm hiding an agenda.<br /><br />"This may be a successful rhetorical or argumentative technique, but it will not lead you to the truth."<br /><br />Yet again you refer to this nonspecific agenda of mine. What is it, exactly? I'm the most interested in hearing what you think I'm doing, as it's beyond me.<br /><br />You ended your message as 'parting'. If you won't be responding despite the unnecessary rehash of your misconceptions, I suppose that's up to you.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-27089792905691291422009-10-10T09:55:19.281-07:002009-10-10T09:55:19.281-07:00Brian, how is commenting on an implication from co...Brian, how is commenting on an implication from complexity -> design off-topic? It's my point 1) that I started out with, it's what you got us derailed on by demanding a single definition of complexity. My example wasn't even about design: it was about dolphin computers. Why not reply to it rather than yet again misrepresenting me? I know I can be accidentally pedantic, but I'm not *that* unclear.<br /><br />"I was asking whether you agree that your statement<br /><br />"complexity never implies design""<br /><br />When did I say that, Brian? Why use double quotes if you're paraphrasing? When did you ask something that appears nowhere in this thread? No, my point is that I've never seen a design from complexity argument which follows, AKA complexity does not imply design. Using the word 'never' can imply a level of certainty restricted to math and logic.<br /><br />Now then, you're asking me if I'm being ambiguous when I say that complexity does not imply design. The answer is: yes and no. I am being ambiguous as to which particular complexity arguments are used as they vary and often don't have a coherent idea of complexity to begin with. There's nothing wrong with that, as for the upteenth time I prefer to refer to all of the arguments touted as such rather than using a restrictive definition and therefore equivocating (as you wish to say I'm already doing). I am being unambiguous concerning their validity or cogency.<br /><br />"It is obviously an ambiguous statement, just as "complexity implies design" is an ambiguous statement. Both statements require further clarification to be meaningful, i.e. "complexity" must be further defined. "<br /><br />Well then it's a good thing I didn't say your lie of a quote, isn't it? I've repeatedly told you precisely what I mean. If you have any problems with my usage as I've clarified, bring them up. Rehashing the same points as if I hadn't already replied is disingenuous.<br /><br />"If you were debating someone who said "complexity implies design," you would recognize it as an ambiguous statement, and you would demand clarification, but you do not hold yourself to this standard."<br /><br />Their claim implies that there is at least one cogent complexity -> design argument, which should be specific enough for that cogency to exist. My claim, as I've repeatedly made it, is that I've seen no complexity arguments which imply design. List one, you'll find it fails. you've already tried and they've already failed. The burden of proof here is on the claimant of the positive claim, not the one with reasoned skepticism of a range of claims.<br /><br />"The fallacy of equivocality occurs when you use the term "complexity" as a synonym for Dr. Hunter's description of finely tuned cellular structures, then later effectively redefine "complexity" as a sloppy, haphazard state of affairs which should be expected as a result of unguided natural forces."<br /><br />I didn't do that, Brian. Somehow, despite me pointing it out, you've misunderstood *again* what the context of messy was. It's astounding that you labor under these false impressions despite my clarification.<br /><br />"You will no doubt deny that you did this; others will have to judge for themselves."<br /><br />Oh, so you do recognize that I pointed it out? Then why not address it rather than repeating yourself? Brow-beating is rather pitiful.<br /><br />"You later seemed to be trying to say that you use the above phrase as some kind of shorthand for a much more complex concept."<br /><br />No, I didn't. I didn't use "the above phrase" because you seem wont to actually quote me. I did use 'messy' as a reference to the process of evolution, though. You know, how I *originally stated the point*: "[...] it's a messy way to go about arriving at the organisms we see."<br /><br />See if you can tell me what is before the ellipsis.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-43023280642811555672009-10-09T20:00:23.045-07:002009-10-09T20:00:23.045-07:00Shirakawasuna:
Your example does not relate to ou...Shirakawasuna:<br /><br />Your example does not relate to our discussion. We are not discussing whether complexity ever implies design. You are repeatedly answering a question that I am not asking.<br /><br />I was asking whether you agree that your statement<br /><br />"complexity never implies design"<br /><br />is an ambiguous statement. <br /><br />It is obviously an ambiguous statement, just as "complexity implies design" is an ambiguous statement. Both statements require further clarification to be meaningful, i.e. "complexity" must be further defined. It is this definition which you will not commit to, which leads to fallacious statements and logic. If you were debating someone who said "complexity implies design," you would recognize it as an ambiguous statement, and you would demand clarification, but you do not hold yourself to this standard.<br /><br />The fallacy of equivocality occurs when you use the term "complexity" as a synonym for Dr. Hunter's description of finely tuned cellular structures, then later effectively redefine "complexity" as a sloppy, haphazard state of affairs which should be expected as a result of unguided natural forces. You will no doubt deny that you did this; others will have to judge for themselves.<br /><br />You later seemed to be trying to say that you use the above phrase as some kind of shorthand for a much more complex concept. I attempted to craft a sentence which I felt restated your position exactly, but you rejected that as well, although I don't understand your objections to my attempt.<br /><br />I thought we could proceed with this discussion, but I don't see it going anywhere. I made a good faith attempt to explain one last time, but it seems to be beyond my powers to make you understand. It appears to me that you wish to hold to a very tightly scripted rejection of design arguments, and resist further admissions which might be "damaging to your case."<br /><br />This may be a successful rhetorical or argumentative technique, but it will not lead you to the truth.<br /><br />I do want to congratulate you on your improved syntax in the last two posts. Sloppy writing both reveals and promotes sloppy thinking.<br /><br />With that, I will give you the last word. Give me your best shot.CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-75885652389868592102009-10-09T13:47:49.149-07:002009-10-09T13:47:49.149-07:00"The *only* way to *avoid* equivocation is to..."The *only* way to *avoid* equivocation is to assign a single definition to "complexity", and if you refuse to do that, for whatever reason, the statement is equivocal."<br /><br />No, you are wrong. Let's try an example.<br /><br />"I say that no personal computers are created solely from dolphins."<br /><br />It's a silly example, but you see the point. I see you as demanding to know the definition of personal computers, and my response would be that I mean it in a general sense: I have seen nothing described as a personal computer which is created solely from dolphins. You might try to offer options: a beige box with a CRT monitor? Any mass-produced computer with a screen? What about headless computers? Do iPhones count since they have a screen, keyboard interface, and more power than many computers satisfying 'beige and mass-produced'?<br /><br />It doesn't matter, I'm describing my experience with arguments claimed or implied to be from complexity in any of its forms (typically fairly vague). You've been getting my point, I suspect, because you keep trying to list some arguments which you think work. So why are we still talking about this?<br /><br />"I (Shirakawasuna) do not accept design from complexity arguments in the field of biology, because I have never seen an example which I judged to be valid."<br /><br />False. I haven't seen any arguments which do complexity -> design successfully anywhere. When a reasonable design inference is made, it's hardly merely citing an abstract or vague form of design but instead finding not merely analogy, by direct overlap between the actions of men (defined as designers) and the object in question.<br /><br />The fallacy of equivocation arises when a definition is used in one part of an argument but changes in the middle, when they are implied to be the same. I have not done this at any point.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-34178650817279925002009-10-08T18:47:28.470-07:002009-10-08T18:47:28.470-07:00Shirakawasuna:
That was clearer; thanks.
You sai...Shirakawasuna:<br /><br />That was clearer; thanks.<br /><br />You said,"complexity does not imply design."<br /><br />I really wasn't listing three alternatives for you to choose from, and asking you to make a false choice. I was explaining three different approaches to understanding your statement, from my standpoint. <br /><br />One makes the above sentence make sense, but is false. Another makes the statement equivocal, or possibly false. The final approach (non-choice) makes the statement equivocal. I can see no way of making the sentence both logical and true, and you have not offered me another alternative.<br /><br />In relation to this, let me clearly respond to your last paragraph:<br /><br />The *only* way to *avoid* equivocation is to assign a single definition to "complexity", and if you refuse to do that, for whatever reason, the statement is equivocal.<br /><br />It seems to me that your response is that:<br /><br />"complexity does not imply design"<br /><br />literally means<br /><br />"I (Shirakawasuna) do not accept design from complexity arguments in the field of biology, because I have never seen an example which I judged to be valid."<br /><br />Those two statements are not equivalent. If that is what you mean, that's what you should say, because this statement:<br /><br />"complexity does not imply design."<br /><br />is equivocal (when "complexity" is undefined), as I have repeatedly demonstrated, and any reasoning based on that statement is fallacious.<br /><br />Agreed?CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-49674367389300733892009-10-08T16:59:16.919-07:002009-10-08T16:59:16.919-07:00Brian, I appreciate (again) the civil tone, but th...Brian, I appreciate (again) the civil tone, but the answer you seek has been written three times with respect to defining complexity. I used it as a blanket term: I have seen no situation where complexity implies design, in fact it's often clearly and obviously fallacious as the person using it doesn't understand the subject matter.<br /><br />You listed three specific options for me to choose. I choose 4), which should really be 1), as I listed it before, as I'm referring to design from complexity arguments in general without equivocating by using only one of the definitions.<br /><br />I have said this many times, so why don't you address it? I'm using a general catch-all term for its uses, particularly with respect to design. I've seen no serious complexity -> design arguments which are not fallacious. I'm repeating myself.<br /><br />With respect to your specific definitions, I've clarified what 'messy' referred to. When I originally mentioned messy, it wasn't even in reference to this point but to a mechanism. What are you still confused about?<br /><br />I have seen no 'fine-tuning' arguments which are not fallacious, Brian. In fact, what they lack in coherence they often make up for in short-sightedness, but I digress. I have also dealt with your attempt at proving by example the accuracy of some design arguments and rejected them for a very good reason: choosing something known to have been made by people, then saying it's fine-tuned, then claiming that you made the reverse inference is post-hoc rationalization.<br /><br />To repeat myself yet again, I was making a general reference to design arguments based on complexity. They don't follow, Brian. Defining complexity as a single version would be equivocating and it's what I avoided by using a general reference. This is probably the fourth time I've said that as well, with no response.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-64625153282796342572009-10-08T15:19:55.914-07:002009-10-08T15:19:55.914-07:00Shirakawasuna:
Sorry for the delayed response; it...Shirakawasuna:<br /><br />Sorry for the delayed response; it was unavoidable. I hope you are still watching this post.<br /><br />Let me reassure you that I did not merely skim your replies, but read them several times to try and make sense of them. I also did not intend to use any unfair tactics to make my points while closing down discussion. I don't mind you having the last word, but it seemed to me that we couldn't agree on terms, so further discussion was fruitless.<br /><br />I thought you were being deliberately obtuse, but you seem to feel misunderstood, and I will admit the possibility that I misunderstand what you said. You use a lot of run-on sentences with unclear subject/verb relationships which are difficult to follow. I am willing to give it one last try, if you are game, but let's have a disciplined discussion, in clear English. <br /><br />In your last reply, you made this clear statement to me:<br /><br />"If your premises were accurate, you would have identified fallacies."<br /><br />That is very fair-minded of you to say, and I think it is a starting place for a reasonable discussion. Were my premises accurate? <br /><br />I don't want to re-hash the whole discussion yet. I want to re-state my argument once more, as clearly as possible, and let you have a chance to respond, as clearly as possible, and perhaps we can move on from there.<br /><br />Once more, then:<br /><br />1. EQUIVOCALITY:<br /><br />You made the direct statement that "complexity does not imply design." You seem to think I didn't recognize the directness of your statement, but the directness of your statement is not the issue. What is at issue is whether you maintain a true and consistent definition of "complexity."<br /><br />I see basically three possibilities:<br /><br />1. If you define "complex" as "messy" as in "disorganized", then your statement would be logical, but it would also be false. The cell is demonstrably not messy, in the sense of being disorganized. It is highly organized; we could not live if it were not.<br /><br />2. On the other hand, if you define "complex" as "exquisitely ordered and fine-tuned," then your sentence may be true or untrue. Human technology is marked by exquisite order and fine-tuning, and the nature of its order is what allows us to infer that it is designed. Therefore, this definition makes your statement either false or illogical because of equivocality.<br /><br />3. If, in fact, you can't define the term complex for me or yourself, then your statement is certainly ambiguous, or equivocal in meaning, in which case you have committed the fallacy of equivocation.<br /><br />So, my question is how do YOU define complexity for yourself, when YOU make the statement, "Complexity does not imply design?" Please do not complain about how others use it. You are the one who made the statement, and I want to know what YOU mean when YOU say that.<br /><br />If we are successful at working this one out, maybe we can take a crack at some of the other issues you raised.CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-46730437225217679572009-10-07T09:17:03.193-07:002009-10-07T09:17:03.193-07:00It's strange that you declare no more response...It's strange that you declare no more response, then set out to say three more paragraphs, but I'll gladly respond.<br /><br />"There is also no point in continuing our other debates if you refuse to define terms, or accept common-sense definitions of words like "complex" and "information"."<br /><br />My term was a blanket term. Throw any argument from complexity at me, it will surely apply. I've explained this many times. I am not sticking a single definition into yours or anyone else's mouth(s). *That* would be equivocation, and it's what I avoided.<br /><br />A common-sense definition of information is too vague for you to make half-decent arguments for design, arguments that have a terrible track record to begin with. How can you presume to tell me what information implies for a biological structure if you can't quantify it or precisely define what information is important for design for it versus that for other chemical phenomena? Appealing to an intuition, one for which the word 'complex' likely applies better than 'has lots of information', does not an argument make. I do understand the common-sense meaning, I just refuse to acknowledge that they have the rigor required.<br /><br />"Finally, it is remarkable to me that you claim in your last response that you have the ability to recognize design in human technology on sight, even if you came across it in a random place in space. Then, you claim the inability to recognize design in an artifact which possesses much greater complexity and order."<br /><br />If you would refer again to what I wrote, I did not use a fallacious complexity/order -> design argument. That's the specialty of ID proponents, remember?<br /><br />You finish up by implying that the post's point was to indicate an 'exquisitely tuned' system and that my interpretation of this as an argument for design is suggestive of presumably unwanted qualities in myself. I would ask you to read, "Fine Tuning and the Intellectual Necessity" from May 17 if you honestly expect me to believe such garbage. He has used fine-tuning before, in respect to biology, and it's use is/was in attacking evolution and implying design (interchangeable in the ID movement).<br /><br />There are called-for and juvenile rephrasings of what you tried to sell me, but I'll refrain.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-27618580991585767902009-10-07T09:16:37.729-07:002009-10-07T09:16:37.729-07:00Anonymous: A protein changing in response to the b...Anonymous: A protein changing in response to the binding of another protein happens all the time. It's how your immune system recognizes non-self compounds (antigens).<br /><br />Brian: Yet again you ignore my responses, or at least give them a cheap skimming and repeat yourself. We aren't getting anywhere because you're stuck on your original false premise, which is that you understood what I was saying. Despite my clarification, you labor under that impression.<br /><br />"I contend that they were both classic examples of logical fallacy, by simple definition. To my mind, they could be used as teaching examples (perhaps they may)."<br /><br />If your premises were accurate, you would have identified fallacies. However, your premises are inaccurate and I have explained why. That you barely acknowledge this difference but plod along anyways is disengenuous.<br /><br />"However, you continue to insist that "there's nothing wrong with being intentionally vague" and admit to using equivocal language, but then deny equivocation."<br /><br />That's right. My being vague in that situation is not equivocation, it's making a blanket statement. My statement does not require the modification of any use of the word(s) invoked in the argument nor the implication of a false definition. As such, it does not satisfy the fallacy of equivocation.<br /><br />"Furthermore, you continue to rest arguments against irreducible complexity on the assumption that irreducible complexity has been scientifically disproven (when it has not) and then deny begging the question."<br /><br />Undemonstrated, all of it. You'll have to do better than inaccurately rephrasing my points, Brian. Quote me.<br /><br />Your next comment is a declaration that you won't continue. That's up to you, of course, but this embarrassingly bad-faith effort of yours, despite its appreciated civil tone, hardly stands on its own merits. You have misunderstood, despite clarification, and refuse to acknowledge it. You ignore further clarifications. You ignore the arguments explaining your misidentification of fallacies.Unknownhttps://www.blogger.com/profile/00983894183615070865noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-89197418388979980882009-10-06T21:20:43.103-07:002009-10-06T21:20:43.103-07:00Shirakawasuna:
Congratulations on your long reply...Shirakawasuna:<br /><br />Congratulations on your long reply. You are obviously an energetic typist.<br /><br />It may have seemed like I was being elusive, but actually I was just trying to keep to the main point of our exchange, which was whether the two points you made in your first comment were logically fallacious.<br /><br />It seems we will not reach an agreement on the matter. I contend that they were both classic examples of logical fallacy, by simple definition. To my mind, they could be used as teaching examples (perhaps they may).<br /><br />However, you continue to insist that "there's nothing wrong with being intentionally vague" and admit to using equivocal language, but then deny equivocation.<br /><br />Furthermore, you continue to rest arguments against irreducible complexity on the assumption that irreducible complexity has been scientifically disproven (when it has not) and then deny begging the question.<br /><br />I have no further interest in arguing these points with you anymore. I will leave it to others to judge who is right.<br /><br />There is also no point in continuing our other debates if you refuse to define terms, or accept common-sense definitions of words like "complex" and "information".<br /><br />Finally, it is remarkable to me that you claim in your last response that you have the ability to recognize design in human technology on sight, even if you came across it in a random place in space. Then, you claim the inability to recognize design in an artifact which possesses much greater complexity and order.<br /><br />Indeed, your whole response to Dr. Hunter's post is telling. All he did was quote an evolutionist researcher who said that he had found an "exquisitely tuned" mechanosensory system in the cell. He then agreed with the evolutionist that this is yet another example of life's "exquisite tuning," which is true. He did not state in this post that fine-tuning implies intelligent design. Your mind is the one that made that inference. It is suggestive, isn't it?CotnerMDhttps://www.blogger.com/profile/05464641116473121903noreply@blogger.comtag:blogger.com,1999:blog-3855268335402896473.post-34703472878716101142009-10-06T07:59:47.901-07:002009-10-06T07:59:47.901-07:00But how did codependency evolve? Did it start as o...But how did codependency evolve? Did it start as one protein, then another protein joined up? But that means that the frist protein had to change to accomodate the second protein. And this had to happen simultaniously.Anonymousnoreply@blogger.com