HTML5 Flash Player (Shumway) lands in Mozilla
41–50 of 181 posts
Re: HTML5 Flash Player (Shumway) lands in Mozilla
#42Earlier quoted context omitted.
Why would Adobe do something like this? It costs them money and it doesn't improve their position (and IMO, their goals) at all.
From where does Adobe get money from Flash? It isn't through the Flash Player plugins (which are already free), but it does get money from tools that create Flash content. So why wouldn't it make sense for Adobe to have made a move like this?
Re: HTML5 Flash Player (Shumway) lands in Mozilla
#43Earlier quoted context omitted.
There's no real conceptual difference between a element, a element, a WebGL experience, a NaCl app or a Flash on your webpage. They're all somewhat non-semantic, hard to search, rich media black boxes. So what's your particular beef with Flash, especially when rendered via HTML5? Or do you just hate all tools that enable creativity beyond a plain text website equally? Or did you just drink the Flash-should-die KoolAi…
Yes there is. You misunderstand. My beef is with NaCl, objects, Applets and ActiveX etc as well, mainly because they run outside of the browser's engine, sandbox, security model and conceptual model. you also have to ship them externally to the browser. Canvas, video, webgl fine.
Re: HTML5 Flash Player (Shumway) lands in Mozilla
#44Earlier quoted context omitted.
Yes there is. You misunderstand. My beef is with NaCl, objects, Applets and ActiveX etc as well, mainly because they run outside of the browser's engine, sandbox, security model and conceptual model. you also have to ship them externally to the browser. Canvas, video, webgl fine.
From the fine article: "Shumway is an HTML5 technology experiment that explores building a faithful and efficient renderer for the SWF file format without native code assistance." By your criteria, you should be fine with this.
Re: HTML5 Flash Player (Shumway) lands in Mozilla
#45Nothing beats the ease with which the regular flash player can be blocked, and then occasionally loaded by mouse click as it works with flash block and the like. The danger of it becoming an extension is that it's now more difficult to have that block/override workflow. And there's always the dreadful prospect of people embedding it directly into their site, potentially leading to a new wave of blanket JavaScript blo…
Re: HTML5 Flash Player (Shumway) lands in Mozilla
#46Earlier quoted context omitted.
Yes there is. You misunderstand. My beef is with NaCl, objects, Applets and ActiveX etc as well, mainly because they run outside of the browser's engine, sandbox, security model and conceptual model. you also have to ship them externally to the browser. Canvas, video, webgl fine.
What's so great about the "security model" of the browser? It's a patch work of horrible decisions.
But one security model is better than having two security models.
Re: HTML5 Flash Player (Shumway) lands in Mozilla
#47I tried to use it ~1 month ago, it wasn't a great experience. I tried playing video and several games on Kongregate, and almost nothing worked, except Flash ads (only few games showed anything similar to loading screen -- most of them just didn't start at all). But the most problematic thing was its slowness. Even small almost static ads brought entire Firefox to its knees. I am looking forward for this project, but…
Re: HTML5 Flash Player (Shumway) lands in Mozilla
#48Why not to convert flash stuff to html5 directly? Using runtime is just extra overhead.
Re: HTML5 Flash Player (Shumway) lands in Mozilla
#49Why not to convert flash stuff to html5 directly? Using runtime is just extra overhead.
That would be the ideal case. However, that would require the cooperation of the owners of all this Flash stuff, and there is simply no way to get them all to agree to get rid of Flash just because the reference implementation happens to be annoying, crash-prone, unsafe, etc. So, in practice, the only way to handle the issue is to do stuff at runtime.
Re: HTML5 Flash Player (Shumway) lands in Mozilla
#50Nothing beats the ease with which the regular flash player can be blocked, and then occasionally loaded by mouse click as it works with flash block and the like. The danger of it becoming an extension is that it's now more difficult to have that block/override workflow. And there's always the dreadful prospect of people embedding it directly into their site, potentially leading to a new wave of blanket JavaScript blo…
Too bad. The browser is becoming general purpose with asm.js, WebGL etc. You can't hold back progress.