if the app was fast , i'm sure everybody would be positive. IT is not.I dont even get 1 fps on my MCBOOK PRO. Explain me how i can enjoy beauty that way.
I would be worried about the health of your computer. My work's T420 lenovo doesn't seem to lag THAT much, in fact, I hadn't noticed much of it until I got to read the comments here...
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.
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.
Interesting, I've never heard that criticism of NaCl before. I guess it makes some sense if you're engineering toward a "thin client" model with cheap, minimalist hardware.
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."
The problem isn't so much with WebGL performance. WebGL is easily fast enough for simple particles like this (although 2D canvas could probably also manage it). The problem is that a lot of web devs don't have a full understanding of the OpenGL pipeline, and how using tools and effects in one way rather than another can lead to crippling performance issues. That entire scene could probably be batched into a single render call.
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.
I'm taking a break in an office environment. I scan various sites for interesting stories which I open in new tabs, then I read the stories of interest.
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.)
As more of an art project that is trying to play on the user's emotions, I think it's appropriate. There has to be section of the web which is allowed to engage people outside of the cubicle. The specific context of your office sounds like a great chance to apply the mute function.
No, it is still an issue. Those icons are fairly small, if I have many tabs open it can take a moment for my eyes to scan across the tabs to locate the playing icon.
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.
I'm a bit confused as to what it means by disappearing, or how to stop it. Does the site chronologically delete memories or does it all go down as memories aren't added?
I've yet to meet a high-end 3D game that my machine can't run at 40fps+. I'm really impressed that they've managed to make it chug along at 3fps displaying glowy dots.
