The above sentence is true, but it has no bearing on anything.
The fact that they weren't reverse-engineered (yet) would still have huge bearing on everything.
By 7 billion samples I mean the humans walking around. Your analogy with an RSA crack is fundamentally different beccause biology doesn't do it in 3 pounds of grey goo in seven billion different bodies already.
so you would have to come up with an analogy that uses something we cant use, to say, okay fine it exists and fine, we have the hardware to also do it, but the former doesn't have any bearing on us doing the latter.
Still it wouldn't help us find the P-time algorithm in question. We could say "it seems to exist", but that would not imply "we'll discover it any day now".
> If brains routinely cracked RSA
For brains numbers have a completely different meaning and internal representation than for computers. Brains don't "think in numbers". Doing the kind of math we invented is a major effort for the brain, it's not what it developed for, and it is very poorly equipped to do explicit numerical calculations (emphasis on "explicit"). So looking at brains to "crack RSA" seems like waiting for a hammer to be useful in driving screws. > i.e. the amount of computation that human neural nets can likely be doing
We don't know nearly enough what they are really doing! We only know a few selected bits and pieces! You are basing your assumptions on nothing, so according to logic any conclusion is possible from a faulty premise. On which you promptly deliver spectacularly.Also, the "computation" a brain does at one moment leaves out the time aspect: Lots of things lead to constant changes. The wiring changes all the time. The "computation" metaphor has little use for describing or understanding this major aspect of "brain". The more I learned about neuroscience the more unhappy I got with the computing metaphor that I had had going in (as a CS graduate, naturally, I think). The brain is so very, very different from my pre-neuroscience-courses notions.
How much neuroscience do you know? If the answer isn't at least an undergrad introductory course (the accompanying book is over a thousand pages), why do you get the idea you can make any predictions?
Read this to read about complexity in biology vs. engineering and what scientists in the field think how well we are dealing with it:
- http://biorxiv.org/content/early/2016/05/26/055624
- http://www.cell.com/cancer-cell/fulltext/S1535-6108(02)00133...
Test yourself: Do you understand what he's talking about? http://inference-review.com/article/the-excitable-mitochondr...
Fortunately you don't have to sign up at university these days just for such knowledge:
Free courses (if you ignore the certificate nonsense):
- https://www.mcb80x.org/ (This is linked to from edX as "The Fundamentals of Neuroscience" Parts 1, 2, 3)
- https://www.coursera.org/courses?languages=en&query=neurosci... (Especially "Medical Neuroscience": https://www.coursera.org/learn/medical-neuroscience)
>As an IT guy with a basic but solid neuroscience education
-- could you go ahead and take a few minutes (maybe will take you 5-10) to read through my above-referenced links referencing my previous discussion and tell me whether I'm correct in your estimation on the bottom-up aspect - i.e. the amount of computation that human neural nets can likely be doing, and how it compares to server farms with fast interconnects today?
I'm not an expert in neuroscience so your feedback might be helpful there.