Google is becoming more like Wolfram. Semantic search engine all the way to go.
Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
51–60 of 146 posts
Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
#52This works great in Firefox 11. It doesn't work in Chrome 18 which has WebGL disabled (on Linux). EDIT: I really doesn't work because "NVIDIA cards with nouveau drivers in Linux are crash-prone." Firefox has no trouble, strangely.
After fiddling with about:flags and using --ignore-gpu-blacklist on the command line, I got chrome://gpu to report that WebGL is fully enabled. It _still_ doesn't work, with this error reported in the console: [75:75:1827873622829:ERROR:command_buffer_proxy.cc(110)] Could not send GpuCommandBufferMsg_Initialize.
I suppose you need the latest mesa and drm. It works great here, but I'm running code from git.
Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
#53Aw. Whatever this query does, it doesn't do it in Mobile Safari :(
Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
#54very cool. what i made for the lulz: https://www.google.com/search?btnG=1&pws=0&q=sqrt(x*...
Haha I was about to post the same thing.
sqrt(xx+yyy)+3cos(sqrt(xx+yy))+5
Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
#55This works great in Firefox 11. It doesn't work in Chrome 18 which has WebGL disabled (on Linux). EDIT: I really doesn't work because "NVIDIA cards with nouveau drivers in Linux are crash-prone." Firefox has no trouble, strangely.
> It doesn't work in Chrome 18 which has WebGL disabled (on Linux).
Chrome 18 on Ubuntu 11.04 with real crappy Intel Mobile 4 Chipset and it works.
Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
#56is that a sombrero?
It's more like a Devo hat...
Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
#57Earlier quoted context omitted.
I simply didn't understand. His post doesn't say anything about WebGL not being supported by his GPU specifically, though obviously that's a problem. I guess I don't know what he wants? Yes, if your browser and system isn't supported... what do you want? Do we expect Google to have to support every user, for every nonessential, nonrevenue-producing feature? Maybe I'm just missing something, but it seems I was punishe…
You were making unfounded assumptions (that enabling WebGL would be as trivial as installing Chrome) and at the same time ignored the fact that you get highly useful results from WA without any plugins or bleeding-edge tech. Having good fallbacks is important.
Yikes. A lot of 'you' accusations there.
>You were making unfounded assumptions (that enabling WebGL would be as trivial as installing Chrome)
No, I made the point that installing Chrome is trivial and the message explicitly states that your system simply might not be capable. If that's the case, what is Google supposed to do? Just render an empty grid and make a "whah-wha" noise?
>at the same time ignored the fact that you get highly useful results from WA without any plugins or bleeding-edge tech
No I didn't. At all. I am not saying this is an "answer" or a competitor to WolframAlpha. This is a trivial feature that was thrown in. It's non-essential and I bet you'll never ever see Google pushing a browser plugin on any of their sites save for some existing exceptions (Talk). As you've noted, there are tons of places to go besides Google for a 3d graph.
>Having good fallbacks is important.
When it doesn't require confusing your user, or compromising standards to ask them to install a gargantuan plugin.
edit: If the whole point of this was merely to clean up the error message or simply suppress it on unsupported browsers, then sure, but like I said, I genuinely just didn't understand the sarcasm, my apologies.
Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
#58Earlier quoted context omitted.
He might mean that this computer doesn't have a card/driver combo capable of running WebGL. This is actually fairly common from test Mozilla has carried out. Successfull WebGL context creation on Windows were bellow 70% (can't find the actual page with the real numbers right now). But Chrome now supports software rendering through swiftshaders which should help those people. I for one agree with you, even with the is…
I simply didn't understand. His post doesn't say anything about WebGL not being supported by his GPU specifically, though obviously that's a problem. I guess I don't know what he wants? Yes, if your browser and system isn't supported... what do you want? Do we expect Google to have to support every user, for every nonessential, nonrevenue-producing feature? Maybe I'm just missing something, but it seems I was punishe…
Well, if I was Google, I probably wouldn't make an error message the top search result.
I am running Chrome on a Thinkpad, so it's not like I can actually do anything to fix the error.
Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
#59Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20
#60Earlier quoted context omitted.
He might mean that this computer doesn't have a card/driver combo capable of running WebGL. This is actually fairly common from test Mozilla has carried out. Successfull WebGL context creation on Windows were bellow 70% (can't find the actual page with the real numbers right now). But Chrome now supports software rendering through swiftshaders which should help those people. I for one agree with you, even with the is…
I simply didn't understand. His post doesn't say anything about WebGL not being supported by his GPU specifically, though obviously that's a problem. I guess I don't know what he wants? Yes, if your browser and system isn't supported... what do you want? Do we expect Google to have to support every user, for every nonessential, nonrevenue-producing feature? Maybe I'm just missing something, but it seems I was punishe…
You basically equated the hassle of getting WebGL working if someone is on a browser without it to the hassle of getting Wolfram Alpha Pro.
What you are missing is that if you don't have Wolfram Alpha Pro, the regular plain old Wolfram Alpha still plots it for you. It gives you a 3D view and a contour map, and throws in a couple series expansion and the derivative. You don't get the fancy interactivity without Pro, but you get to see what the thing is.
At Google, on the other hand, you either get the full 3D interactive experience, or you get "3D charts require a web browser and system that support WebGL".