Wedge
Public area => The Pub => Off-topic => Topic started by: Dismal Shadow on November 19th, 2011, 10:40 AM
-
This made me smile. 8-)
http://occupyflash.org/
-
What's wrong with Flash? It's far more powerful than HTML, CSS and JS and a ton of games are available which are made in flash.
-
It's also badly implemented, meaning that despite supposedly operating as a form of virtual machine, it frequently bleeds memory, eats CPU time, and is still surprisingly sieve-like for security.
-
Just for the record -- heavy HTML5 sites also have a history of crashing my various browsers... :whistle:
-
Personally never liked flash that much, seems HTML5 may be the road to take.
Seems Adobe have just given up on Adobe Flash for mobile I believe.
-
Flash on mobile was a bad idea, most of the Flash apps don't respond well (if at all) to touch events, not even mimicking regular mouse events, and it is a huge CPU draw.
HTML5 can be abused too, but it's actually a little harder to abuse than Flash is.
-
Personally never liked flash that much, seems HTML5 may be the road to take.
-
It's only because Flash has better support for codecs than the other browsers do, and then it's mostly political rather than practical as to why different browsers support what they do.
-
It's not about codecs, it's about 3D programming. Especially for games.
-
Right now, codecs are the issue, as far as the video/audio issues that Nao mentioned are concerned.
But 3D programming going forward will be a big thing, especially if browsers are reticent about implementing WebGL, which they are for valid security reasons.
-
I think the WebGL issue is closer to resolution by now... Although I'm not a specialist on the issue. (But I do want to look into doing some 3D coding in the future. Would be nice to get in touch with my earlier life as a 3D dev... Only in a browser. Best of both worlds.)
-
I don't think it's close enough that either Mozilla or Opera want to reintegrate it yet, anyway, but it's an interesting notion that the video memory isn't protected properly.
-
?
Opera has 'reintegrated' it -- rather, integrated it, since it only was a test version before that... Now it's an alpha, which is a bit closer, and hopefully should be a beta before the end of the year. (Normally, Opera releases stable versions in December, but it would seem that this year they're having issues with HW acceleration so they're probably postponing it to early '12.)
BTW, WebGL != HW acceleration, as I'm currently running v12 and I can assure you that even with HW acceleration off, WebGL works perfectly well.
-
Oh, they reintegrated it?
I was under the impression that WebGL actually depended on HW acceleration to actually function :/
-
Oh, they reintegrated it?
I was under the impression that WebGL actually depended on HW acceleration to actually function :/
WebGL objects are shown on a canvas, AFAIK. You could easily get away with creating a software surface for the page itself, and have a canvas surface that's rendered through Direct3D, OpenGL or whatever. Just like OpenGL has always worked in regular Windows windows (sure..), i.e. software GDI mixed with hardware surface for OpenGL. At least that was the case back in 1999, I see no reason why this would have changed...
-
Well, it's been in the 12.00 alpha for a few weeks, now. Maybe a couple of months. They actually planned to have it in 11.50 but postponed it to 12.00 probably because it was a 'big' feature.
WebGL objects are shown on a canvas, AFAIK. You could easily get away with creating a software surface for the page itself, and have a canvas surface that's rendered through Direct3D, OpenGL or whatever. Just like OpenGL has always worked in regular Windows windows (sure..), i.e. software GDI mixed with hardware surface for OpenGL. At least that was the case back in 1999, I see no reason why this would have changed...
-
OOP should help make it easier to implement :P
-
TBH without HW acceleration WebGL would be quit limited, as CPU can't compete with GPU when it comes to rendering speed.
-
As I said -- WebGL does use HW acceleration, but on its own surface, because GPUs are smart enough to be able to enable HW acceleration just for a small area.
-
Hopefully WebGL catches on, then Flash will start to seem old.
-
Limited ain't the word, I've seen it on Chrome, and it is painful, very painful.
-
WebGL in Chrome is bad..?
-
It was... some versions ago. Even a really limited demo was kicking out a single digit FPS count on my machine.
-
Must have been with disabled HW acceleration, I suppose!
Okay, last post!
-
Come to think of it, it may have been before HW acceleration was added, will have to try again.
-
Didn't they completely removed it?
-
I have no idea what they have, or have not, done.
-
Chrome dev has WebGL support and it's the fastest around. They also have HW accel.
Opera has WebGL and HW accel in 12.00, and you can disable HW accel but still have WebGL. I haven't tested WebGL performance with HW activated.
-
Hmm, interesting. I wonder if there are any good benchmarks/test sites around to showcase what WebGL can do, and do well.
-
I think it can do anything... Although using textures is probably a bit overkill if you don't want to use too much bandwidth.
I'm sure I could do KMJ in webgl. Just not sure it'd be worth the hassle.