Earlier quoted context omitted.
Which is why iOS should be avoided too. They may appear to be playing kind of nice now, but they won't forever. That blatant disregard for openness is a sure sign they're going to end up the same way, no matter what they say now.
> iOS should be avoided too What would you suggest using?
Choose Firefox Now, or Later You Won't Get a Choice (2014)
331–340 of 343 posts
Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)
#332Just so we can avoid rehashing the discussion whenever a post encouraging the use of Firefox is posted. - Yes, Mozilla is still the better browser when it comes to privacy. - Yes, Mozilla has made missteps with Pocket and Mr. Robot. - Yes, it is slow/resource heavy on certain Macs with non-default resolutions. Yes, Mozilla is working on a fix. - Yes, it has become really fast for most users after Quantum improvements…
Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)
#333It's about the worst marketing pitch I can think of.
Tell us reasons to choose Firefox over Chrome. If there are no reasons to prefer Firefox, it doesn't matter whether we lose the ability to choose it.
Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)
#334I used to donate to Mozilla, but ever since they fired Brendan I haven't been able to look at them the same way. I use Firefox daily, but actually don't really care if they die because it's their own fault.
Brendan Eich wasn't fired, he stepped down.
> “We didn’t act like you’d expect Mozilla to act,” wrote Mozilla Executive Chairwoman Mitchell Baker in a blog post. “We didn’t move fast enough to engage with people once the controversy started. We’re sorry.”
Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)
#335Earlier quoted context omitted.
"- No, you can't just "fork Chromium" if you don't like the way Google is running the project. Web developers will still make their website work well with whatever Google releases, regardless of standards." Hah, even compiling Chromium takes a huge amount of effort and a workday or so of time. Don't think I'd want to go spelunking through that codebase
I would imagine that compiling Firefox is just as difficult.
Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)
#336Genuinely curious - how is it that people don’t trust the website they have an account/email/bank with, but still trust plug-ins that now have access to all your browser activity
Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)
#337Is there any way to make Firefox use the passwords I have saved with Google (available at passwords.google.com and loaded into gnome-keyring)?
Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)
#338Earlier quoted context omitted.
I use both firefox and chrome. Chrome does have user profiles, and I can have multiple open at once. Separate cookies but ALSO separate extensions.
You may not have been suggesting otherwise, but in case you're not aware, Firefox also has user profiles and can have multiple open at once.
unless I am mistaken and -no-remote isnt required anymore.
Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)
#339Earlier quoted context omitted.
> Firefox in Firefox OS was slow and it gave me a feeling that firefox was not for mobile (but I guess it's not true anymore) I genuinely don't understand how Firefox on mobile is slow. I hear this complaint often (along with the complaint of Firefox on desktop not being able to run certain websites, which also never occurs to me), but for how much I try, I never managed to make Firefox on mobile (android) slow. Ther…
Firefox on Android has a notable scrolling delay which drives me nuts. iOS guarantees that the point where your finger first makes contact remains under that finger as you scroll. Most good Android apps can deliver on this promise 99%, but for some reason, Firefox on Android does not.
Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)
#340Earlier quoted context omitted.
They can use Firefox, just not the rendering engine. I expect that would still be considered an adequate move. Nobody I know (bias) has an iOS device and no laptop or PC, so they can also adopt it on their PC.
How is using reskinned Safari with WebKit rendering engine considered adequate move? That would be like putting a Firefox skin over IE6 engine a few years back - it would not help the ecosystem in the way this article asks for.