Initially Microsoft didn’t want the boatload of crap that comes with Flash to ruin your PC experience (lag, battery drain and security vulnerabilities). But Adobe and MS worked together to make a custom version for Win8. Initially sites were restricted to only permit sites that had ‘good’ Flash in use (excluding Desktop Win8 which was unrestricted). But as of tomorrow they will do the opposite- all sites will be enabled to run Flash unless they do not handle Flash properly in which case they are on a restricted list (noted at about 4% of all sites). So I’ll be checking for updates starting tonight (yes I’m impatient). Good Flash is good. Bad Flash is very bad. Looks like MS moved the ball…well played.


  1. Microsoft says yes to Flash and no to Silverlight on RT.

    Sorry to hear this, thought Microsoft had exhibited some interest in the anti-Flash movement Steve Jobs set in motion resulting in Adobe declaring an exit for Flash Player from the entire mobile business. Thought they were going for no IE10 plugins altogether. Now, less pressure to shove the web even farther to HTML5.

    So your link says it makes these good/bad distinctions mostly based on attempts to trigger ActiveX control somehow. Wouldn’t a lot of the important Flash some people need (like the organizations that kept clinging to IE6) involve ActiveX, not just animations and video? How do they make some sort of battery usage criteria, don’t Flash videos (a common use of Flash) and anything animated tend to eat up the battery about as voraciously as each other?

    If there’s bad Flash, why don’t they send out Flash design software and Flash Player updates to suppress this code from being made/played on their own?

Comments are closed.