3 ms·
It's interesting computation, but how often is it useful to quickly estimate how many people were living in China between 1950 and 1980? Not to pick on that on
by snowwrestler 13y ago
It's interesting computation, but how often is it useful to quickly estimate how many people were living in China between 1950 and 1980?
Not to pick on that one example, but I do think this is part of the reason that Wolfram Alpha has not taken off at consumer scale. It seems to me that the things it can do that Google cannot, while technologically impressive, are not particularly valuable to most people.
After completing their schooling, most people don't need to solve equations every day. If they do, they already have ways of doing it (Mathematica, for example).
And most people don't need to look up census data, or historical GDP tables, or the location of the ISS. And if they do, they already have ways to do that.
Basically, Wolfram's approach seems like a great way to organize and make useful knowledge that is fully known. But the most value is pushing the edge of the unknown, and that means continuously taking in, indexing, and presenting new information. Facebook does this, Twitter does this, Stack Overflow does this, etc....and Google indexes all of that.
- ams6110 13y agoIt might be a good way to solve those stupid interview questions like "how many manhole covers are in Manhattan"
- kens 13y agoSlight tangent: If you haven't seen the ISS go overhead, you really should do so - it's pretty cool. To find on when to see it: http://spotthestation.nasa.gov/sightings http://spotthestation.nasa.gov/sightings
- MaulingMonkey 13y ago> And if they do, they already have ways to do that. Disseparate ways that take awhile, with results from multiple sources that need to be manually combined to figure out what information is worthwhile. Some of the random queries I've tossed into WA: "If the average mailbox size is 57MB, and I've only processed 65% of one in the past half hour, how long is it going to take to proce ss all 80GB?" Q: http://www.wolframalpha.com/input/?i=30+min+%2F+%2857MB+*+0.65%29+%3D+x+month%2F+80GB http://www.wolframalpha.com/input/?i=30+min+%2F+%2857MB+*+0.... A: ~1.5 months, better come up with an alternative "How big is a gigasecond?" Q: http://www.wolframalpha.com/input/?i=1+gigasecond http://www.wolframalpha.com/input/?i=1+gigasecond A: ~1/3rd of a century "Just how fast are my 5m/s Kerbal Space Program landings?" Q: http://www.wolframalpha.com/input/?i=5m%2Fs+to+mph http://www.wolframalpha.com/input/?i=5m%2Fs+to+mph A: "I've been rear ended at that speed" "How much precision will a double give me at the radius of pluto?" Q: http://www.wolframalpha.com/input/?i=orbit+radius+of+pluto+%2F+%282+**+53%29 http://www.wolframalpha.com/input/?i=orbit+radius+of+pluto+%... A: "millimeter, perfect" Or work related; "I'm having trouble visualizing these 3d points, please plot them so I can get a better mental picture for why this right angle assertion is triggering" "Divide by b squared? That can't be right..." when canceling out terms in math code for efficiency, rearriving at one of the equations of http://en.wikipedia.org/wiki/Vector_projection#Vector_projection_2 http://en.wikipedia.org/wiki/Vector_projection#Vector_projec... . "I can't intuit the behavior of this math without graphing it out, lets see... bounds... period... yeah that makes sense!" I also use it for simpler calculations: "How do the prices of gold and platinum stack up against each other?" "How long until sunset? Thanksgiving?" "When is 18 KST in my timezone?" "How much is that in dollars?" "How big is an acre?" "What does the compound interest on that look like?" Some of these could be found through google... probably followed by trolling the results for a specific calculator. Others I could calculate myself. But most would be inconvenient enough without WA I wouldn't ask them. Some of these are idle curiosity, but others have saved me significant time doing my job. It's not a daily sort of thing, but it's a consistent way to answer these oddball questions for myself. Google was a tool I had to learn to turn to with my problems. It didn't used to be my primary interface to all documentation, for example... slowly but surely I turned to it more and more frequently. And so it is so far with me and Wolfram Alpha.
- flavor8 13y agoStill, there are significant holes in the parsing engine - once you learn its quirks you can get around it, but it's a long way from natural. It can do, for example: "estimated number of atoms in a liter of water" - http://www.wolframalpha.com/input/?i=estimated+number+of+atoms+in+a+liter+of+water http://www.wolframalpha.com/input/?i=estimated+number+of+ato... and "volume of a cup of coffee" http://www.wolframalpha.com/input/?i=volume+of+a+cup+of+coffee http://www.wolframalpha.com/input/?i=volume+of+a+cup+of+coff... but not: "estimated number of atoms in a cup of coffee" http://www.wolframalpha.com/input/?i=estimated+number+of+atoms+in+a+cup+of+coffee http://www.wolframalpha.com/input/?i=estimated+number+of+ato... What you're looking for is: "estimated number of atoms in 1 cup of water". Similarly "distance to moon in terms of bill gates' height" does NOT work, while "distance to moon / bill gates' height" does work.
- MaulingMonkey 13y agoQuite true. Still, the same holds for Google as well - sometimes you need to avoid relevant keywords because of the junk they'll bring in, other times you need to add seemingly tangential keywords, and yet other times you need to resort to google's syntax -- quotation marks, +/- and site: prefixes. (alack, poor +, we hardly knew ye) Stumbling upon the right combination can take quite a bit of work until you've built up experience with both the search engine and the subject material's keywords.