undefined | Better HN

0 pointsdarklycan512y ago0 comments

Might be the case now (Note, I'm talking about Nightly), this was a few years back, I noticed that first it warned that a new version was working and then mysteriously bricked the browser after, complained and they told me that I "shouldn't be using nightly if I don't wanna have the latest updates"... which I do, but I don't wanna be forced into a restart unless it actually breaks?

0 comments

Dalewyn2y ago

Firefox Nightly is a branch specifically for testing and evaluating the newest updates. If you want reliability and consistency out of Nightly, the problem is you.

You will get what you want out of the regular branch, and even more out of the Extended Support Release branch.

As for Windows rebooting out of nowhere: Get a Professional or Enterprise license and turn autoupdates off via Group Policy and your problems are solved.

darklycan51OP2y ago

And this is exactly the comment I was talking about.

Anyways for any sensible people, yes, Nightly is a branch specifically for testing and evaluating, doesn't mean you have to brick peoples browsers after some time when you push an update (again, back when I used it that was the behavior, according to a different comment it might be different now), to force a restart.

"As for Windows rebooting out of nowhere: Get a Professional or Enterprise license and turn autoupdates off via Group Policy and your problems are solved.", yes, I already addressed this and mentioned this solution, but again, that doesn't change the fact that it's wrong in the first place, maybe actually read the comment you are replying to?

DiabloD32y ago

I use Nightly exclusively. Unless you are somehow installing Nightly updates in a way that the binary is owned by a user who isn't you (ie, owned by root), Nightly will never force you to restart, it just forever has the green dot on the hamburger menu.

This is true for me on both Windows (and my user is part of the Administrator group, thus can write to a global c:\Program Files install) and Linux (and Firefox is installed to a directory in $HOME to simplify the process of non-packaged binary management).

Now, I also have Firefox (stable) installed as a .deb (to fulfill the browser dep). If the .deb gets upgraded by apt, that Firefox suddenly bricks itself until I restart. And this is intentional, btw, given how Firefox interacts with itself to do process isolation.

Everything I say here has been true for roughly the past decade.

j / k navigate · click thread line to collapse