Path: csiph.com!x330-a1.tempe.blueboxinc.net!aioe.org!.POSTED!not-for-mail From: "javax.swing.JSnarker" Newsgroups: comp.lang.java.programmer Subject: Re: The halting problem revisited Date: Tue, 29 Mar 2011 08:35:17 -0400 Organization: media lab? Lines: 34 Message-ID: References: <8v727mF46lU1@mid.individual.net> <8vbuiaFbm7U1@mid.individual.net> <8vd51lFlq1U1@mid.individual.net> <8ve17fFto9U1@mid.individual.net> NNTP-Posting-Host: otMsOqwtQOIcdZwq0NLlOw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Forte Agent 2.0/32.652 X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:2539 On 29/03/2011 8:22 AM, Dirk Bruere at NeoPax wrote: > On 29/03/2011 12:49, javax.swing.JSnarker wrote: >> On 29/03/2011 12:21 AM, Dirk Bruere at NeoPax wrote: >>> However, I do not believe it is algorithmic. >>> QM randomness seems to be a result of asking questions for which there >>> is no physical answer. >> >> Actually, QM randomness is a symptom of indexical uncertainty about >> which exact universe you're in out of many that look identical up to a >> certain point in time and then diverge, more or less. >> >> In fact, copies of you end up experiencing each possible universe that >> has you in it, so the uncertainty is really about which *you* you are >> out of many that have had thus-far-identical experiences. >> >> Which means the randomness is actually in data from a source external to >> any computer inside the universe. But if you simulated the whole >> multiverse, by just running Schrödinger's wavefunction for the initial >> state forward without collapse, in that simulation would be implicit >> emulations of the smaller computer, each receiving a different random >> bit-string -- and all embedded in a deterministic whole. >> > > That's what I said (in a different way)! > But I agree with you that it is a plausible mechanism in the MWI context Well, in principle there is a "physical answer" in this case, but in practice you can't actually get at it. :) -- public final class JSnarker extends JComponent A JSnarker is an NNTP-aware component that asynchronously provides snarky output when the Ego.needsPuncturing() event is fired in cljp.