Live data from Hacker News

Firefox desktop market share now below 9%

netmarketshare.com

351–360 of 755 posts

Re: Firefox desktop market share now below 9%

#351

Earlier quoted context omitted.

I use Firefox for development, but I use safari (privately) and edge (professionally) for browsing, and see no real advantages to using either Firefox or Chrome for that. I think modern Firefox is a much better browser than Chrome though, but Mozilla certainly lost the PR war and to no fault but their own, because Firefox sure sucked for a long while.

> I think modern Firefox is a much better browser than Chrome though, but Mozilla certainly lost the PR war and to no fault but their own, because Firefox sure sucked for a long while. This gets said often, but I've been using Firefox continually since 2003 and I've never noticed it sucking.

I use FF too, and I notice it sucking periodically, often after a big update - as things will - there have been periods of a month maybe two times in the last 10 years where I had to switch to another browser because it sucked too bad.

Re: Firefox desktop market share now below 9%

#352
post #338

Earlier quoted context omitted.

When you log out, Firefox will block it and warn you that you are about to close number of tabs. When you select "OK", your tabs are gone. But Chrome will quietly exit, and when you start it next time, will offer to restore the tabs that were open last time. Chrome approach wins, hands down.

Both browsers have this configurable in settings. So they just use different defaults, which depends on personal preference.

But which is the natural default? The one where you lose a lot of state seems like a far worse choice.

Re: Firefox desktop market share now below 9%

#353
post #338

Earlier quoted context omitted.

> I think modern Firefox is a much better browser than Chrome though, but Mozilla certainly lost the PR war and to no fault but their own, because Firefox sure sucked for a long while. This gets said often, but I've been using Firefox continually since 2003 and I've never noticed it sucking.

When you log out, Firefox will block it and warn you that you are about to close number of tabs. When you select "OK", your tabs are gone. But Chrome will quietly exit, and when you start it next time, will offer to restore the tabs that were open last time. Chrome approach wins, hands down.

Isn't this google applications will track what you do all the time, and even after you close the application and restart it knows who you are and what you did?

Re: Firefox desktop market share now below 9%

#354

Chrome lost me when it started to force-login me to Chrome when signing into Gmail, thus sharing all my website visits with Google. I switched to FF two months ago and haven't looked back. FF is like Linux: less polished, but works, and you are in control. A fair tradeoff for me.

Everyone complains about privacy, yet a browser forcing you to share what you visit with a website has 60+% market share, which is insane.

The only answer to all this bully behavior is since years only one: Firefox.

A bit slower here and there? It's ok, machines are getting more and more powerful. Your data won't come back, once it's in someone else's hands.

Re: Firefox desktop market share now below 9%

#356
post #342
post #338

Earlier quoted context omitted.

When you log out, Firefox will block it and warn you that you are about to close number of tabs. When you select "OK", your tabs are gone. But Chrome will quietly exit, and when you start it next time, will offer to restore the tabs that were open last time. Chrome approach wins, hands down.

That's a setting in both browsers. Default is "Start with Startpage or empty page" in both browsers as well. You can always select "Restore last session" in both browsers.

The problem is that if Firefox is getting this default wrong, what else are they getting wrong? And it should realize user state is sacred, I would even expect if I quit browser with something written in the address bar (or search bar, etc), when it starts up again, it should be able to preserve this half-entered user input!

Re: Firefox desktop market share now below 9%

#358

What an irony. I've been using firefox for 10+ years and now it is faster, uses less resourses and doesn't crash. As a user, this is the browser I have been waiting for. Yes, dev tools features could be expanded as well as the plugin franework(vimperator!).But these are non-issues for regular users.

The only thing I disliked in so many years is the bunch of imcompatible extensions due to the switch to the new plugin system.

For example, I was unable to use NoScript, because it didn't really work well.

Still, this is something you can forgive considering that for more than 15 years they released always good software.

Re: Firefox desktop market share now below 9%

#359
post #9

Been really enjoying Firefox, especially after Quantum. More devs should support and use it, lest we be beholden to Chrome for the rest of time.

I use Firefox for development, but I use safari (privately) and edge (professionally) for browsing, and see no real advantages to using either Firefox or Chrome for that. I think modern Firefox is a much better browser than Chrome though, but Mozilla certainly lost the PR war and to no fault but their own, because Firefox sure sucked for a long while.

Firefox sucking wasn't their own fault? I would say it was. I would also say that their continued bloating of firefox and ancilliary projects/services shows that they still haven't return to their original mission.

Re: Firefox desktop market share now below 9%

#360

Earlier quoted context omitted.

This can be helpful in development scenarios. I’m supporting a team that uses localstack to support local development against some AWS services. Unfortunately, the CORS settings for localstack break the development environment. With Chrome allowing them to disable from the command-line, I can provide a shortcut to launch with degraded security, no plugins, no user settings, etc. My only wish is that Chrome would make…

Why not just configure your server or a proxy to add the necessary headers that unlock CORS restrictions.

Because having code that behaves differently on development and production is never a solution, it's a workaround. Having bugs that can't be reproduced locally is the worst thing that can happen to a developer. So yeah, you can _just_ put environment settings if you have no other possible way, but you should really avoid it if there is any other one (like using chrome with CORS disabled, here).
Post reply on HN