LLlloeki·Jul 17, 2012
> I'm not sure it's entirely relevant, but here's something the very-very senior flash dev at work said about that recent Dart port of the Flash API (which he thought was neat).
>>> "This little game was developed with Flash and later ported to HTML5 in only 6 hours. The new HTML5 version runs with smooth 60fps, which is almost impossible to achieve
with the Flash plugin!"
>> This is the kind of sentiment that shits me. Flash is measured by the worst of its developers.
>> Flash is capped at 60fps in the browser so as to limit the carnage, but can run at 120+ on the desktop. If the dude can't get his example game running at 60 fps in flash it's because he sucks, not the plugin. /rant
As far as I understand it, the API[0] author highlighted that the HTML5 port was consistently over 60fps (or constantly at 60fps if capped), whereas the Flas
Read the rest
h version was consistently under 60fps, and not even reaching the limit, hence no 60fps capping could be coming into play.
> Similarly, be prepared for a slew of super slow "HTML5" apps.
Inevitably, bad code will come. Flash on the web had one advantage: it was dead easy to block.
[0] https://github.com/bp74/dartflash