Choose Firefox Now, or Later You Won't Get a Choice (2014)

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by Yoric on Friday December 07, 2018 @06:12AM (#18626692)

The Chrome multiprocess isolation model is really good. Firefox devs have known this for ages (heck, there were demos of a version of Firefox 3.x with a similar model), but could not actually land this model for two reasons:

- it would break all old-style extensions and users were unhappy about that;

- it takes looooots of memory and users were unhappy about that, too.

Now that Firefox has dropped all old-style extensions, there's large focus on reducing memory footprint, to allow moving to this model without costing as much memory as Chrome.

There are still a few kinks to fix, but this new isolation model should hopefully land within a few months.

Also, all sorts of security improvements are much easier now that Firefox dropped old-style extensions. Also, switching many developments to Rust makes new code much, much safer.

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by andrewl-hn on Friday December 07, 2018 @06:43AM (#18626858)

Also, Firefox isolates the browser UI and Web content into separate processes now. So that all the code you download from the internet doesn't run in the browser process. Same is with plugins.

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by Santosh83 on Friday December 07, 2018 @06:50AM (#18626887)

A browser written in Rust (which is probably Firefox's long term goal) should blow Chrome out of the water in terms of security, despite the massive efforts invested in that regard by Google to prop up Chrome's C++ code base.

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by chris_wot on Friday December 07, 2018 @07:21AM (#18627044)

Would it really though? Sure, there are definitely things about Rust that make coding more secure, but surely that it only one part of security?

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by Yoric on Friday December 07, 2018 @07:44AM (#18627158)

Indeed, that's only one part of security. But it's a pretty big one!

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by tinus_hn on Friday December 07, 2018 @07:36AM (#18627117)

Definitely, it prevents the buffer overflow style of exploits but there’s also a lot of leaks in how all the DOM objects interact.

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by Paul-ish on Friday December 07, 2018 @12:05PM (#18629337)

It seems unlikely that FF will ever be completely written in Rust. More likely that new bits that get added are Rust, and many of the old bits stay C++.

If FF gets rewritten in Rust, it will be a decades long effort.

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by pietroglyph on Friday December 07, 2018 @12:28PM (#18629546)

I would just add that Mozilla also targets security critical portions with Rust rewrites. You don't necessarily need 100% Rust to be secure (if you have the right security model).

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by SilasX on Friday December 07, 2018 @09:50AM (#18628084)

Google doesn’t have military grade static analysis that rejects anything that could allow buffer overflow attacks?

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by Rusky on Friday December 07, 2018 @02:19PM (#18630663)

No, they don't, because such a thing cannot exist for C++. Any attempt would basically recreate Rust, or something equivalently incompatible with existing C++ codebases.

[ Parent | on HN ]