2 ms·
But we both know it wont in the real world. We also know that Adobe will probably change the Flash output slightly in the future, and Gnash will always be a ste
by UnknownSource 16y ago
But we both know it wont in the real world. We also know that Adobe will probably change the Flash output slightly in the future, and Gnash will always be a step behind.
It doesn't change the fact that you would be wasting development resources, because you then have duplicate functionality. Why waste resources on developing an addon, which will need to be updated with the browser api's, for many browsers, and optimised, when the browsers themselves already have the functionality built in? If resources are spent optimising the browsers themselves rather than a foreign addon, every website benefits.
Fact is, the same problem's we've had with flash addon in the past (such as in cases where updating the browser caused crashes), will still exist in Gnash player instead.
Why are you so eager to encourage people to duplicate functionality browsers are building into their core code these days?
You can either improve the browser, or you can improve Gnash. Both are open source. Unless there is something the flash standard can do which open standards couldn't?
- rbanffy 16y agoThere are lots of applications, in embedded devices, that are built with Flash and target Gnash instead of the Adobe runtime. Gnash is reasonably good and supports hardware-acceleration. I agree we should move over to HTML5 as soon as possible (taking encumbered codecs in consideration), but some flash support is a nice to have, even if it's not full support.