Flash as a CPU hog is a user complaint. Users do not care how it compares to other similar technologies and this narrow metric won’t convince any of them. This

Flash as a CPU hog is a user complaint. Users do not care how it compares to other similar technologies and this narrow metric won’t convince any of them. This was a fixable problem that wasn’t fixed. Flash is no longer the king of easy to make visual extravaganza. It was apparent to those who used Flash because they couldn’t pile on extravaganza effects like they saw in Processing. Flash did not even address their concerns for years, if they listened to core users the performance complains from the rest of the web would have resolved themselves. Flash should have had hardware acceleration added years ago (not just for video) because it was commonly used to display very taxing animations. Multiple out of view banner ads were a common use case, Flash had no built in ability to disable out of view banners that did not need to run, or API to enable background tasks that needed to be run. Most banners were made with AS2 and Flash still does not have an auto updating mechanism apart from Chrome. HTML5 Canvas will get hardware acceleration eventually, WebGL will have it from the start. The difference is Flash was around for years doing those things, shoving ever more taxing animations while ignoring usage scenarios and the economics of Flash projects. (where developers satisfy clients, not users) I expect browsers will pay more attention to usage scenarios, since they make their money when people use the web, Adobe makes it from selling tools. tl;dr – If Flash or Canvas feel like CPU hogs that needs to be fixed, whatever it takes. Put in CPU usage limits, don’t let people compile CPU hogs, APIs for background tasks, add 20MB of hardware acceleration to the runtime, contribute to WebKit, Firefox, NativeClient to get it resolved. Should have prioritized this earlier, now kiss your penetration goodbye.