3 ms·

You'll also end up with (something like) Flash making a comeback. Nobody's going to accept a non-interactive web, or even one with crippled interactivity[1]. T

You'll also end up with (something like) Flash making a comeback. Nobody's going to accept a non-interactive web, or even one with crippled interactivity[1]. They only tolerated it in the 90s due to hardware and bandwidth limitations, not to mention that the web was new technology back then. That ship has long since sailed. Even back then, technologies such as Flash arose because people - initially website owners/creators and then, of course, users - wanted more interactivity than HTML 3.2 and 4.x, and slow/limited JavaScript, could deliver. [1] With very few exceptions, the GP being one.

eitland 8y ago
> Nobody's going to accept a non-interactive web, or even one with crippled interactivity I don't talk about that: I talk about limiting web pages from using unreasonable amounts of client side resources. We're not talking about a lack of interactivity. We're talking about webpages - loading the page, then leaving the CPU alone - not running crypto miners (at least not without asking) - not having all the time in the world to run timing attacks
AnIdiotOnTheNet 8y ago
> You'll also end up with (something like) Flash making a comeback Something like Flash did make a comeback and it's just called JavaScript now. Pretty much exactly the same attack surface, but at least now its a hopelessly complicated "standard"!
- bartread 8y ago
  > Pretty much exactly the same attack surface, but at least now its a hopelessly complicated "standard"! I know, right? I almost miss Flash: it was certainly a lot simpler to work with. I'm not even sure about the "almost" in that sentence.
- johncolanduoni 8y ago
  > Pretty much exactly the same attack surface Flash exploits were a lot more commonplace and frankly embarrassing than what you see in JS engines these days, so I have trouble seeing it as the same attacking surface.

eitland 8y ago

> Nobody's going to accept a non-interactive web, or even one with crippled interactivity I don't talk about that: I talk about limiting web pages from using unreasonable amounts of client side resources. We're not talking about a lack of interactivity. We're talking about webpages - loading the page, then leaving the CPU alone - not running crypto miners (at least not without asking) - not having all the time in the world to run timing attacks

AnIdiotOnTheNet 8y ago

> You'll also end up with (something like) Flash making a comeback Something like Flash did make a comeback and it's just called JavaScript now. Pretty much exactly the same attack surface, but at least now its a hopelessly complicated "standard"!

bartread 8y ago
> Pretty much exactly the same attack surface, but at least now its a hopelessly complicated "standard"! I know, right? I almost miss Flash: it was certainly a lot simpler to work with. I'm not even sure about the "almost" in that sentence.
johncolanduoni 8y ago
> Pretty much exactly the same attack surface Flash exploits were a lot more commonplace and frankly embarrassing than what you see in JS engines these days, so I have trouble seeing it as the same attacking surface.