32 ms·
> If you have a better approach that accomplishes both of those objectives, do tell. Use a browser that isolates the JS engine in its own process and leave spe
by msbarnett 5y ago
> If you have a better approach that accomplishes both of those objectives, do tell.
Use a browser that isolates the JS engine in its own process and leave spectre mitigations enabled rather than try to play kid-plugging-holes-in-dike-with-finger by auditing all the world’s constantly-changing JS for spectre/meltdown gadgets?
- SkyMarshal 5y ago>Use a browser that isolates the JS engine in its own process Definitely. All for that. >and leave spectre mitigations enabled I do that anyway. The performance cost is unnoticeable to my normal workloads. >rather than try to play kid-plugging-holes-in-dike-with-finger by auditing all the world’s constantly-changing JS for spectre/meltdown gadgets? I'll continue doing this too, largely because I want to see what's going on behind the scenes on all the websites I visit. Useful for me to see it all, especially as it changes over time as you observe. That said, Easylist and Privacylist are also great if you'd rather crowd-source the finger-in-dike-hole-plugging.