Re:HTML5 Flash Player (Shumway) lands in Mozilla
by biot on Wednesday October 02, 2013 @06:15AM
(#6481588)
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
by spongle on Wednesday October 02, 2013 @07:07AM
(#6481740)
Well if it wasn't for the numer of turtles in the pile on the way down it'd be fine. This is a whole other layer on top...
Re:HTML5 Flash Player (Shumway) lands in Mozilla
by riquito on Wednesday October 02, 2013 @06:48AM
(#6481684)
You end up seeing a canvas, does it matter what application was used to draw it? (by the way I don't like Flash either for different reasons)
Re:HTML5 Flash Player (Shumway) lands in Mozilla
by roarroar on Wednesday October 02, 2013 @07:05AM
(#6481737)
What's so great about the "security model" of the browser? It's a patch work of horrible decisions.
Re:HTML5 Flash Player (Shumway) lands in Mozilla
by spongle on Wednesday October 02, 2013 @07:07AM
(#6481744)
Nothing at all. It's shit.
But one security model is better than having two security models.
Re:HTML5 Flash Player (Shumway) lands in Mozilla
by captainmuon on Wednesday October 02, 2013 @07:42AM
(#6481845)
If the components are sufficiently isolated, I'd much rather have many smaller components (with individual security models) than one monolithic system.
That's why e.g. the Unity3d plugin is so great. A complete 3D engine (with state of the art graphics, the ability to load almost any 3d format on earth, ...) does not belong into the browser. I don't want that code on my work PC.
OTOH, its great to have the ability to run games in the browser. The performance is much better than WebGL (because it contains compiled code, and because it is a complete, tuned, engine and not just an opengl implementation). And it's fairly safe, since it's built with Mono/.NET, you don't have problems with shellcode injection etc..
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.