News for hackers. Stuff that matters.
Re:Google Chrome’s new Meltdown and Spectre safeguard is a m... by staticassertion on Saturday July 14, 2018 @02:53PM (#17531753)
They are not ignoring the issue, but they also do not have this mitigation in place.

Getting there will take a long time. Chrome got lucky - they've been working on this for ages, and they happened to be rolling this out right when Spectre landed.

Re:Google Chrome’s new Meltdown and Spectre safeguard is a m... by Caspy7 on Saturday July 14, 2018 @04:06PM (#17532090)
Firefox is definitely working on this in Project Fission. Bringing down memory per process is crucial and a big focus right now. (I think getting resource sharing down to a science will also be important.)

I'm a fan of Firefox but admit Chrome has an advantage in this situation, while Firefox has had the advantage of resource sharing within the process to keep memory down. Last estimate I saw suggested over a year for it to arrive.

As an illustration of how this approach affects the landscape for all browsers, TechCrunch regularly loads 30 origins on a single page.