4 ms·
And this one: "What's interesting here is how what this really demonstrates is that Flash really was exactly what we wanted". With HTML5, who didn't see annoyi
by koonsolo 9y ago
And this one: "What's interesting here is how what this really demonstrates is that Flash really was exactly what we wanted".
With HTML5, who didn't see annoying JavaScript popups and autoplay videos coming? Seriously.
If you think about the web, think about 2 things:
1. Text content
2. Multimedia content
People complaining about Flash always used arguments for nr 1.
For me, I want my text content to be really static text content, and my multimedia content to be boxed-in multimedia. HTML4 and Flash were good at that. Now you have a mix of both:
1. Text content with annoying interactions
2. Crippled multimedia content (think about the terrible way iOS handles audio for HTML5 games. Expect this in all browsers soon).
- sosborn 9y agoAnnoying stuff is always annoying, but the major complaints about flash were centered on security holes and excessive CPU utilization.
- koonsolo 9y agoSure, I'm willing to accept that, including that Flash is not a web standard. But another solution might have been to make a Flash web standard, with open implementations, instead of HTML5. This is really an architectural choice that was made, not so much the blocking of a plugin. They chose to integrate all in 1 big pile, instead of keeping web content and multimedia separate. And now you end up with a washed out version of both.
- kevin_thibedeau 9y agoNoScript tames all the dark patterns enabled by HTML5.