public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Rodriguez <frodriguez.developer@outlook.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question of quantum computer
Date: Fri, 03 Apr 2015 17:11:11 -0400	[thread overview]
Message-ID: <1478951.WCFfi6fabA@navi> (raw)
In-Reply-To: <CAGfcS_mAG6SsVcZkFLeXp0sEH8-jTAnKHVWBoQUz6+j-_uSESw@mail.gmail.com>

On Friday, April 03, 2015 8:03:12 AM Rich Freeman wrote:
> On Fri, Apr 3, 2015 at 7:06 AM, Peter Humphrey <peter@prh.myzen.co.uk> 
wrote:
> > On Friday 03 April 2015 06:58:38 Rich Freeman wrote:
> >
> >> I'm not convinced that anybody has proven that quantum behavior is truly
> >> non-deterministic
> >
> > But it must be, surely, since it's probabilistic. I don't see how the 
domain
> > of probabilistic behaviour can overlap the domain of deterministic
> > behaviour.
> 
> /me looks over at his handy Plinko board.
> 
> Just because it looks probabilistic, doesn't mean that it is.  Take a
> cryptographic PRNG.  If you know the seed, the output is completely
> deterministic.  If you don't know the seed, you could describe the
> output as probabilistic, and it might look non-deterministic, but it
> still is.

There's an explanation for uncertainty that makes common sense. Let's say I 
throw you a ball, you can catch it because you take many measurements of it's 
location and your brain tries to predict it's path. But this only works 
because the ball is so massive and the photons that we use to see it are 
massless so the effect of them colliding with the ball is neglible. Imagine if 
the only way you could "see" the ball was by throwing another ball at it and 
seeing where it landed, it would then be nearly impossible to predict it's 
path because everytime you measure it you'll get it of course, so the 
principle of uncertainty would hold even though the ball was really on a well 
defined path. See 
http://en.wikipedia.org/wiki/Uncertainty_principle#Heisenberg.27s_microscope

Some claims still boggle my mind (superposition in macroscopic objects), like 
the "tunning fork" (probably a quartz crystal) experiment on this page: 
http://en.wikipedia.org/wiki/Quantum_superposition#Experiments_and_applications
But that's just one sentence stating that the tuning fork can be in a 
superposition of the vibrating and non-vibrating state but I'm sure if you find 
more info about the experiment is not as fantastic as it sounds.

If we ever figure this to be wrong it'll probably just obsolete quantum physics 
so instead of deterministic quantum computing we'll have something else.

 
> The biggest problem I have with quantum mechanics is that there is no
> understanding of underlying mechanisms.  We have models that describe
> experiments, which is great, but not really a satisfying solution.  I

That's the problem with science in general. The one thing it may never be able 
to answer is "why?". Take gravity as an example. We got really good models for 
it, we can predict how it influences even light with great accuracy but what 
are the underlying mechanisms? We may never know.  Einstein would say it's 
because matter bends space, but what is the underlying mechanism for that? We 
just take his word for it because he gave us equations that work better than 
anything else we've come up with so far.


-- 
Fernando Rodriguez


  reply	other threads:[~2015-04-03 21:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 22:33 [gentoo-user] Question of quantum computer Boricua Siempre
2015-04-02 23:25 ` Ivan Viso Altamirano
2015-04-02 23:30   ` Ivan Viso Altamirano
2015-04-02 23:59   ` Fernando Rodriguez
2015-04-02 23:33 ` Ivan Viso Altamirano
2015-04-03  0:07   ` Peter Humphrey
2015-04-03  3:05 ` wabenbau
2015-04-03  3:30   ` wabenbau
2015-04-03 10:58     ` Rich Freeman
2015-04-03 11:06       ` Peter Humphrey
2015-04-03 12:03         ` Rich Freeman
2015-04-03 21:11           ` Fernando Rodriguez [this message]
2015-04-03 23:02             ` [OT] " Peter Humphrey
2015-04-03 23:15               ` Peter Humphrey
2015-04-03 23:24               ` Rich Freeman
2015-04-04  0:31                 ` wabenbau
2015-04-04 11:23                   ` Philip Webb
2015-04-04 11:35                     ` Rich Freeman
2015-04-04 15:41                       ` Alan McKinnon
2015-04-05  4:52                         ` Boricua Siempre
2015-04-05  9:11                           ` Neil Bothwick
2015-04-04  0:36               ` Fernando Rodriguez
2015-04-03 23:30             ` Rich Freeman
2015-04-04  1:27               ` Fernando Rodriguez
2015-04-03 23:57             ` Alan McKinnon
2015-04-04  0:13               ` Fernando Rodriguez
2015-04-04  0:50               ` wabenbau
2015-04-04  3:33                 ` Fernando Rodriguez
2015-04-04  9:08                 ` Alan McKinnon
2015-04-04  2:08         ` Walter Dnes
2015-04-03  6:20   ` Fernando Rodriguez
2015-04-04  2:16     ` wabenbau
2015-04-04  3:37       ` wabenbau
2015-04-04  3:29     ` wabenbau
2015-04-04  1:48 ` microcai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1478951.WCFfi6fabA@navi \
    --to=frodriguez.developer@outlook.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox