>> What I wouldn't give for a search engine with correlation functionality. <<
Yeah, it would be awesome.
>> I'm a grad student in statistics, and it makes me twitchy thinking about how much processing power that would take (never mind writing the program in the first place). <<
Things to consider:
* Tony started coding artificial intelligence at 17.
* JARVIS can render fully detailed 3D holograms in realtime with no apparent bandwidth drain.
* In this case, one of the sets was probably 2-3 dozen sample items from Natasha's stuff. If bandwidth was a concern, crossing that with a thousand or so search results would probably suffice, rather than recrawling the whole of cyberspace.
>> I'm a little surprised at Phil's lack of google-fu, though. I can't figure out if he's really that bad at crafting a search string, or if it's just that it's always feels agonizingly slow to watch somebody else google. <<
Phil is not bad at google-fu. He's searching for something outside of his experience range, which means he doesn't know the vocabulary to bring up the right things quickly -- plus he's searching for a general product type, rather than knowing exactly what he wants already. That slows down the rate.
If he'd gone looking for, say, the President's datebook or a particular model of gun, it wouldn't have taken him more than a minute or few. That's the kind of stuff that Phil handles regularly.
Thoughts
Date: 2014-02-28 06:54 am (UTC)Yeah, it would be awesome.
>> I'm a grad student in statistics, and it makes me twitchy thinking about how much processing power that would take (never mind writing the program in the first place). <<
Things to consider:
* Tony started coding artificial intelligence at 17.
* JARVIS can render fully detailed 3D holograms in realtime with no apparent bandwidth drain.
* In this case, one of the sets was probably 2-3 dozen sample items from Natasha's stuff. If bandwidth was a concern, crossing that with a thousand or so search results would probably suffice, rather than recrawling the whole of cyberspace.
>> I'm a little surprised at Phil's lack of google-fu, though. I can't figure out if he's really that bad at crafting a search string, or if it's just that it's always feels agonizingly slow to watch somebody else google. <<
Phil is not bad at google-fu. He's searching for something outside of his experience range, which means he doesn't know the vocabulary to bring up the right things quickly -- plus he's searching for a general product type, rather than knowing exactly what he wants already. That slows down the rate.
If he'd gone looking for, say, the President's datebook or a particular model of gun, it wouldn't have taken him more than a minute or few. That's the kind of stuff that Phil handles regularly.