The cynical answer is “because it’s convenient for the Chrome team to think that process separation solves everything”…
-
-
Specifically: The lack of e10s + sandboxing was exploited hundreds of times. Clearly implementing both was a huge priority. Spectre: a vuln never exploited in the wild that could conceivably be helped—once OS and HW fixes land—by a project that’s ~3x as much work as e10s. :\
- 7 more replies
New conversation -
-
-
I’m ignorant here (as in most things) - what browser engine was killed by Spectre?
-
EdgeHTML
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.