News for hackers. Stuff that matters.
Re:Rust required to build Gecko by ben0x539 on Friday December 16, 2016 @08:09AM (#13192970)
Rust seems like somewhat of a strategical direction for Firefox, not just any old frivolous dependency like mng support, so I think not prioritizing the brevity of the dependency list is reasonable here.

Have people traditionally been running their own modified browsers? Seems a bit scary given how you'd have to be on the ball to merge security fixes into your branch regularly.

Re:Rust required to build Gecko by gcp on Friday December 16, 2016 @08:14AM (#13192988)
There's a few forks that maintain the old UI that are popular, such as Pale Moon. They get security updates because the old ESR branches they're based on still get security patches from Mozilla.

Of course, that feed of patches will stop at some point. Don't ask me what the contingency plan for those forks is...

Re:Rust required to build Gecko by rebelwebmaster on Friday December 16, 2016 @11:42AM (#13194490)
IIRC, Pale Moon is based off a fork of ESR24, so they're already on their own for any security fix backports at this point.
Re:Rust required to build Gecko by Dylan16807 on Friday December 16, 2016 @03:58PM (#13196742)
I understand the impulse, but you can put the tabs back with a blob of CSS and leave the menus turned on and it's about the same. No need to use a fork for that.