Earlier quoted context omitted.
But Mozilla cannot enforce idealism on the developers. They do already a great job with documentation, but they could and should improve on the dev-tools. Chrome dev tools are now in a state, that I only use them for developing and debugging. Built in code editor with autocomplete. And I can debug ... and change code while debugging. And it works great (mostly). Firefox dev tools on the other hand barely work for me…
I personally prefer firefox's dev tools to chrome's ones.
Firefox has lots of room to improve if it wants to beat Chrome
221–230 of 401 posts
Re: Firefox has lots of room to improve if it wants to beat Chrome
#222For me, I have found Firefox to drain my laptop's battery more (Macbook Pro, 2017) compared to Chrome (and Safari). Once it changes, I would gladly go back to using Firefox.
They are in the process of converting their code to use Core Animation instead of OpenGL to draw to the screen, which will help tremendously with the power consumption issue, so help is on the way.
As a temporary workaround until all those changes land, you can have Firefox opt out of using scaled windows on a retina Mac by getting info on the Firefox app and then checking ”Open in Low Resolution” on the get info panel.
Transparency in Firefox can be turned off by going to about:config, and setting gfx.compositor.glcontext.opaque to true.
Re: Firefox has lots of room to improve if it wants to beat Chrome
#223Everyone's talking about what Firefox should do to beat chrome, and meanwhile here I am still suffering the bug that makes it unusable for many MacBooks with retina screens set to "more space". Start Firefox and fans are blaring in seconds, hundreds of reports, years of waiting and no solution... Maybe making it usable in one of the most common devices for devs would be a start, I've got a full building of coworkers…
Simply idling Firefox on my Mac would use almost the same amount of battery as actively browsing Safari. I love Firefox on my home Linux desktop, but that's as far as my love goes at the moment.
Re: Firefox has lots of room to improve if it wants to beat Chrome
#224I feel there's an opening for mobile experience on Android. Chrome is pretty terrible in that space. No extensions, no reader mode, no eacape from AMP, etc.
I think kiwi browser(1) is great in this regard. It supports almost all the chrome extensions including ublock, reader mode, etc. It also has a mode which automatically redirects to non-AMP version of site automatically. (1) https://www.google.com/search?q=kiwi+browser+android
Also the browser itself tends to be a version or two behind which isn't particularly comforting either.
Re: Firefox has lots of room to improve if it wants to beat Chrome
#225I haven't really met anyone who is particularly bothered by these issues. They certainly should be addressed to some degree, but the issues I find people are bothered about in Firefox are something that Mozilla has very little control over: Bugs in sites. As a full-time firefox user, I commonly find that sites have bugs, and when I boot it up in Chrome just to check my hunch, they don't manifest. It's pretty easy to…
> As a full-time firefox user, I commonly find that sites have bugs, and when I boot it up in Chrome just to check my hunch, they don't manifest. Also a full-time Firefox user. This is fascinating because I quite literally cannot remember a website for which I had to switch browser so it would start working. What kind of websites are these? Have you noticed any pattern about them? Perhaps it's a certain type of site…
Every damn time.
Re: Firefox has lots of room to improve if it wants to beat Chrome
#226Earlier quoted context omitted.
But Mozilla cannot enforce idealism on the developers. They do already a great job with documentation, but they could and should improve on the dev-tools. Chrome dev tools are now in a state, that I only use them for developing and debugging. Built in code editor with autocomplete. And I can debug ... and change code while debugging. And it works great (mostly). Firefox dev tools on the other hand barely work for me…
I personally prefer firefox's dev tools to chrome's ones.
Re: Firefox has lots of room to improve if it wants to beat Chrome
#227Firefox has plenty of room for improvement, but this article doesn't touch on it. 1. People don't install their own browser, unless they're on a new computer and want the browser they've always used — people are conservative when making technological choices and when they switch browsers, it's often because they get a friend to install it for them, or they buy a new computer, or install some app that tricks them into…
Re: Firefox has lots of room to improve if it wants to beat Chrome
#228Everyone's talking about what Firefox should do to beat chrome, and meanwhile here I am still suffering the bug that makes it unusable for many MacBooks with retina screens set to "more space". Start Firefox and fans are blaring in seconds, hundreds of reports, years of waiting and no solution... Maybe making it usable in one of the most common devices for devs would be a start, I've got a full building of coworkers…
Re: Firefox has lots of room to improve if it wants to beat Chrome
#229> This raises some questions: why is Firefox usage going down, and what does Mozilla need to do to bring it back up? > How does an average user get started with Firefox? This misses the elephant in the room : the main reason Chrome is eating other browsers is that Google is putting its advertising might behind it. You know that little "want a better browser" pop-up displayed on Google's search engine? That's an absol…
>> that little "want a better browser" pop-up displayed on Google's search engine? I actually do not know what you're talking about. Been using Firefox for the last few years and haven't seen this pop-up once.
https://i.judge.sh/any/Diamond/WindowsSandbox_hE75Eaor7Z.png
Re: Firefox has lots of room to improve if it wants to beat Chrome
#230I haven't really met anyone who is particularly bothered by these issues. They certainly should be addressed to some degree, but the issues I find people are bothered about in Firefox are something that Mozilla has very little control over: Bugs in sites. As a full-time firefox user, I commonly find that sites have bugs, and when I boot it up in Chrome just to check my hunch, they don't manifest. It's pretty easy to…
> As a full-time firefox user, I commonly find that sites have bugs, and when I boot it up in Chrome just to check my hunch, they don't manifest. Also a full-time Firefox user. This is fascinating because I quite literally cannot remember a website for which I had to switch browser so it would start working. What kind of websites are these? Have you noticed any pattern about them? Perhaps it's a certain type of site…