Live data from Hacker News

Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20

google.com

41–50 of 146 posts

Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20

#41

This looks... erm ... neat. A "sophomore OpenGL term project" kind of neat. Wolfram on the other hand does the graphs right [0], which hardly surprising given their 20 years of head start. On a more general note, this reminds me of old Microsoft's tactics. Google should really stick to the search, but instead they throw together something that mimics competitor's feature. Something that looks more featureful and whic…

[0] looks identical over the same ranges of x,y,z. http://goo.gl/pTrLh

Who cares if it's trivial? It's functional, fast, convenient and doesn't require a bunch of cruft. Kinda damages your quasi-rant to find out that you simply... didn't compare the graphs over the same interval. I don't know why every small feature that Google adds is either apparently out of fear of someone who's hardly a competitor or is proof that Google is the next Microsoft (which is a useless statement anyway).

This all just reminds me how truly sad HN's markup is. I can't even escape the multiplication in the query for Google to get it to render properly (I replaced it with a Goo.gl link).

Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20

#43
post #31

Earlier quoted context omitted.

Of course, since this is a Google result, it can just fail and say "3D charts require a web browser and system that support WebGL." Which is super useful to me.

I can't tell if you're being sarcastic about it being super useful. If you are, it seems easier still to download Chrome to do a 3d render then it is to buy WA pro and download an apparently enormous plugin to do the same render

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 issue of webgl capable hardware is much better than having to deal with huge plugins. (I'm biased, I use WebGL for my current work).

Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20

#44
post #43

Earlier quoted context omitted.

I can't tell if you're being sarcastic about it being super useful. If you are, it seems easier still to download Chrome to do a 3d render then it is to buy WA pro and download an apparently enormous plugin to do the same render

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 punished for asking.

Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20

#45
post #19

This 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.

This works great in Firefox 11. It doesn't work in Chrome 18 which has WebGL disabled (on Linux). I am also using Firefox on Linux and was actually suprised this worked. I assumed WebGL was still disabled by default for us.

Nope it's been on for a while but it will only work if you have good OpenGL drivers. (About ~50% of Linux users who try are able to view WebGL content from mozilla's numbers).

Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20

#46

This 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.

Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20

#47

This looks... erm ... neat. A "sophomore OpenGL term project" kind of neat. Wolfram on the other hand does the graphs right [0], which hardly surprising given their 20 years of head start. On a more general note, this reminds me of old Microsoft's tactics. Google should really stick to the search, but instead they throw together something that mimics competitor's feature. Something that looks more featureful and whic…

Well, if i want a quick inspection this wins because i can rotate it without having to download other stuff.

Re: Sqrt(x*x+y*y)+3*cos(sqrt(x*x+y*y))+5 from -20 to 20

#48
post #43

Earlier 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 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.
Post reply on HN