41–50 of 166 posts
So let me get this straight. They break global keyboard shortcuts, which people could use to play/pause media on different websites three years ago: https://bugzilla.mozilla.org/show_bug.cgi?id=1411795 and instead of fixing that, they introduce this shit? Fuck Mozilla. I am already using Waterfox, looks like that wont be changing any time soon.
Earlier quoted context omitted.
Yeah, Mozilla is not what it used to be. I guess it's just wishful thinking that makes it so easy to forget.
They just pushed an update on android on me that disabled all addons except uBO because they don't support them yet, a few hours ago. That was the last straw that broke the camels back for me, after using FF since 1.0. Just rm -rf'd my firefox profile on my desktop a few minutes ago. I've defended them for a long time even if I didn't agree with everything they did, but they're so completely off the rails, enough is…
So let me get this straight. They break global keyboard shortcuts, which people could use to play/pause media on different websites three years ago: https://bugzilla.mozilla.org/show_bug.cgi?id=1411795 and instead of fixing that, they introduce this shit? Fuck Mozilla. I am already using Waterfox, looks like that wont be changing any time soon.
Unless they only have one engineer, adding a new feature is not at the expense of fixing one bug.
Earlier quoted context omitted.
They just pushed an update on android on me that disabled all addons except uBO because they don't support them yet, a few hours ago. That was the last straw that broke the camels back for me, after using FF since 1.0. Just rm -rf'd my firefox profile on my desktop a few minutes ago. I've defended them for a long time even if I didn't agree with everything they did, but they're so completely off the rails, enough is…
What browser are you going to use now? Any tips?
Earlier quoted context omitted.
Unless they only have one engineer, adding a new feature is not at the expense of fixing one bug.
Yet somehow they haven't allocated 1/N engineers to fix a 3 year old accessibility bug.
It may just be that fixing accessibility bugs just doesn't produce much "profit".
I'm sorry, but cloud based speech recognition in itself would already be a red flag, even if Mozilla was doing it in-house. Outsourcing it to Google though? I feel like a company as ostensibly privacy-focused as Mozilla should really know better by now...
Yeah, Mozilla is not what it used to be. I guess it's just wishful thinking that makes it so easy to forget.
Earlier quoted context omitted.
Yeah, Mozilla is not what it used to be. I guess it's just wishful thinking that makes it so easy to forget.
They just pushed an update on android on me that disabled all addons except uBO because they don't support them yet, a few hours ago. That was the last straw that broke the camels back for me, after using FF since 1.0. Just rm -rf'd my firefox profile on my desktop a few minutes ago. I've defended them for a long time even if I didn't agree with everything they did, but they're so completely off the rails, enough is…
But hey, at least these days I get the benefit of having to use two completely separate methods to tell Pocket to get the hell out of my browser.
Earlier quoted context omitted.
Yeah, Mozilla is not what it used to be. I guess it's just wishful thinking that makes it so easy to forget.
They just pushed an update on android on me that disabled all addons except uBO because they don't support them yet, a few hours ago. That was the last straw that broke the camels back for me, after using FF since 1.0. Just rm -rf'd my firefox profile on my desktop a few minutes ago. I've defended them for a long time even if I didn't agree with everything they did, but they're so completely off the rails, enough is…