Oh yeah, I live dangerously too. If it breaks, I can fix it and the total effort of fixing the random problems that happen is less than I would spend reading patch notes.
But, we got newbies here and we gotta teach 'em right from wrong.
Why tho? I never complained about the way it is, I use testing/nightly/beta/alpha everywhere and I rarely have problems. Also with FF. I was more ranting about myself not realizing that the requirement was gone, considering I, multiple times, upgraded and then e.g. opened a few tabs after, which usually prompted for a restart. And in the end, it’s not gonna change anything, as the point of nightly is to catch any bugs and instabilities, which would very likely only occur after a restart of FF.
Watch out, we got a badass over here. Running a nightly build and not reading the patch notes, so brave.
Sometimes I’m too tired and/or lazy to read through dozens of commits on their repo
Oh yeah, I live dangerously too. If it breaks, I can fix it and the total effort of fixing the random problems that happen is less than I would spend reading patch notes.
But, we got newbies here and we gotta teach 'em right from wrong.
You have to learn the rules before you can know when it’s okay to break them
99% of problems I have with arch testing can be resolved by simply downgrading a package, if I can’t fix it by any other means
Then use the releases, that’s literally what they’re for.
Why tho? I never complained about the way it is, I use testing/nightly/beta/alpha everywhere and I rarely have problems. Also with FF. I was more ranting about myself not realizing that the requirement was gone, considering I, multiple times, upgraded and then e.g. opened a few tabs after, which usually prompted for a restart. And in the end, it’s not gonna change anything, as the point of nightly is to catch any bugs and instabilities, which would very likely only occur after a restart of FF.