this post was submitted on 02 Jun 2024
1328 points (97.5% liked)

Memes

45158 readers
3120 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] NikkiDimes@lemmy.world 2 points 3 months ago (3 children)

What is literally one thing Chrome can do that Firefox cannot? Cause I can tell you right now, after tomorrow, only one can block ads.

[–] spicystraw@lemmy.world 4 points 3 months ago

To be fair, Chrome does generally render most websites faster and correctly. I have Chrome installed just in case of some webpages not working with Firefox. Now, that's not Mozillas fault, but from user standpoint makes Chrome more attractive browser to use.

[–] themagzuz@lemmy.blahaj.zone 4 points 3 months ago (2 children)

WebGPU, WebHID and h.265 are all unsupported on firefox

that said, i still daily drive firefox with mostly no problems, but saying that it can do everything chrome can is just flat out wrong

this is by design mind you, chrome have a big enough market share that they can basically just add whatever they want to the web standards and all other browsers just have to try to keep up. i imagine that's part of the reason that chromium skins are so widespread

[–] Percy_JW@kbin.zerstoererbande.de 1 points 3 months ago

Though webgpu is coming and h.265 support only kinda there on chrome and all chromium forks

[–] NikkiDimes@lemmy.world 1 points 3 months ago

I feel like including WebGPU and WebHID is kind of unfair. They are both still in the working draft state as far as web standards go and are experimental. Codec support, on the other hand, is fair though.

[–] lazylion_ca@lemmy.ca 1 points 3 months ago* (last edited 3 months ago) (1 children)

Skip the ssl error message. I log into IP addresses all day and that flag is sanity saving.

[–] optissima@possumpat.io 1 points 3 months ago

have you tried changing security.ssl.enable_ocsp_stapling to false in your about:config?