Firefox

17857 readers

1 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 5 years ago

MODERATORS

k_o_t@lemmy.ml

Why I use Firefox (xn--ime-zza.eu)

submitted 1 year ago by Ninjazzon to c/firefox@lemmy.ml

7 comments fedilink hide all child comments

Questions like “Which browser should I use?” regularly come up on the r/browsers subreddit. I sometimes respond to these posts, but my quick replies usually only contain one or two points. To be honest, until recently I wasn’t even sure myself why I use Firefox. Of course it’s a pretty good browser, but that doesn’t explain why I’ve stubbornly stayed loyal to Firefox for more than a decade. After giving it a bit more thought, I came up with the following reasons.

all 8 comments

sorted by: hot top controversial new old

[–] altima_neo@lemmy.zip 20 points 1 year ago

Because its the best.

[–] N0x0n@lemmy.ml 9 points 1 year ago

What's great about native firefox is that you STILL can tinker arround to improve privacy/security and shape it how you want.

Don't know how long it will last though ^^" One day I'm certain I will have to switch and I will really miss my little buddy :(.

[–] SevereLow@lemmy.world 3 points 1 year ago (1 children)

I use it because I love how the Gecko engine renders web pages. For some reason, Gecko renders fonts way better than the Chromium engine, that is literally bashing my eyes. There's something terribly wrong with the Chromium rendering... and I don't know what it is 😅

[–] banghida@lemm.ee 1 points 1 year ago

True

[–] NoiseColor@startrek.website 3 points 1 year ago (1 children)

I use it too and there is much to like. But there is also another side of it. I'm working in Web sites and apps and regularly test sites and Web apps on many browsers and Firefox has by far the most issues. Sometimes really strange issues that we spend way too much time to fix for Firefox users and lately we just don't.

[–] groet@feddit.de 3 points 1 year ago

Chrome doesn't care about closing html tags. If they are mising the document is invalid but chrome will render it anyway and just add the closing tag where it thinks it should be.

At the other end, Firefox goes beyond the standard and will block certain connections that should be allowed by the fetch standard (the setting to disable that is called enhanced tracking protection).

So chrome allows things things it shouldn't while Firefox blocks some it shouldn't