3 ms·

Somebody please explain to me why ripping out the JS JIT wouldn't work.

• dfrage 7y ago
  In the most recent discussion of this it was reported that is no longer an easy option with Firefox: https://news.ycombinator.com/item?id=20012750 https://news.ycombinator.com/item?id=20012750 There's also a general impression that would be too slow for many web pages, and that comment noted it took minutes for logins using JavaScript cryptography to execute.
  • gpderetta 7y ago
    It seems to me that most people will be willing to pay for slower js as opposed to an overall slower system.
    • zzzcpan 7y ago
      Does it even need to be slower? Almost every single website out there is not a javascript app and so side channel attacks can be mitigated by simply having an rlimit-style CPU time limit after say a user action on a tab.