WebGL is fancy,but performances are just not there yet. How long most people will stay on that site given how slow it is?and i have a pretty good computer(Macbook pro). it's not a geek website, webdevs should test performances seriously and ask themself if these kind of stunts are worth the effort. So yeah, there is a wow effect, but if i was the client,i'd be afraid of a pretty high bounce rate.
The message is clearly lost here,due to performance problems.
i was sitting at a google dev day once, and they were showing off all the cool new stuff you can do with canvas.
the crowd was cheering. google was the rockstar in the house.
my friend sitting next to me turns to me and says:
"great, now we can do what flash could 10 years ago".
that was the same year when the google munich chrome lead was bashing the nacl presenter in a private conversation for being backwards. he "couldn't comprehend it at all" "the cloud should be doing all the work".
yeah no shit, with all the junk layers we're putting on top of one another there's no way the clients can actually compute things themselves.
The main concern about NaCl though, is that it's not portable, it's just Google's version of ActiveX.
So I guess he could have just said "great, now we can do what ActiveX could 10 years ago."
WebGL has lots of potential to be lightweight and non-intrusive. I've started writing a series on the topic to try and dispel some myths of WebGL being slow and bloated.
https://medium.com/p/abf669857722
Part 1 of the technical aspects: https://medium.com/p/cebd176c281d
Every time I see a WebGL site, my NVIDIA card jumps to full usage, followed by increase of CPU usage across all cores.
For real OpenGL stuff, native is the way to go.
During the scan-and-open process, I started to hear bizarre enviro-music and was wondering who was being so inconsiderate.
Fortunately, this page was one of the first I'd opened, so it didn't take too long for my obnoxious self to stop bothering everyone.
(Just ranting about sites with autoplay sound, it's only been a bad idea since day one.)
What chrome should do is take the capability that lets them know if a tab is playing sound and use it to mute that sound, unless the user requests otherwise or perhaps unless the tab is actually being displayed to the user.
What web developers should do is stop autoplaying things with sound. Unless your website is dedicated to things with sound and your user already knows that (read: unless your site is youtube, or vimeo) then autoplaying sound is always the wrong thing to do.
This is a BEAUTIFUL website. "Booh, autoplay!" "Booh, performance!" "Booh, webgl bloat!"
Holy crap guys. 24 comments, only TWO positive ones.
Scratch that, just after I wrote last paragraph I opened the site on Chrome (Instead of FF) and it lags heavily in there. I don't know if it might be because some FF plug ins block third party things like facebook connect and Google analytics...
I find it weird, the difference of fps between Chrome and FF with this site is HUGE in my computer.
