|
|
|
|
|
by Tloewald
3954 days ago
|
|
Flash's speed on desktops is not the main strike against it, although it was actually quite bad for many things (the 3d stuff worked better for it because it bypassed its aging 2d rendering engine which no-one left at Adobe understood or could fix). Flash's speed on mobile was abysmal and Adobe tried and failed to fix it for years (after Steve Jobs' famously pointed all this stuff out). The fact that Flash would store user information separately from the browser in such a way as to circumvent security and privacy models, and did so for years after Macromedia (i.e. pre-Adobe-merger) knew about it, and that Flash had and has as many vulnerabilities as any two operating systems is simply icing on the cake. Here's a discussion -- also from 2010 -- of Flash's abysmal 2d performance (which entailed fixing an example created explicitly to show how awesome Flash was): http://loewald.com/blog/?p=3362 Bear in mind, this is Flash's nearly 20-year-old/mature rendering engine optimized to only do minimal screen updates against a five minute hack using a canvas. And, finally, you need Javascript anyway. Flash actually needs Javascript to even load properly (thanks to the stupid Eolas lawsuit), so it's a case of giving up one evil dictator while keeping a not-nearly-so-evil-and-much-more-useful dictator. |
|
That, plus flashes uncanny ability to peg a process at 100% for seemingly just moving images about made me not a huge fan. This doesn't mean javascript isn't getting as bad or worse now that things are moving to there, but at least the javascript engines aren't as horrible as the flash runtime was. But if these javascript ads start burning cpu and draining energy from my laptop battery there will be a whole lot more sites getting added to my local firewall rules.