this post was submitted on 28 Jun 2023
100 points (98.1% liked)

PC Master Race

14970 readers
1 users here now

A community for PC Master Race.

Rules:

  1. No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
  2. Be respectful. Everyone should feel welcome here.
  3. No NSFW content.
  4. No Ads / Spamming.
  5. Be thoughtful and helpful: even with ‘stupid’ questions. The world won’t be made better or worse by snarky comments schooling naive newcomers on Lemmy.

Notes:

founded 1 year ago
MODERATORS
Brunbrun6766@lemmy.world
_MoveSwiftly@lemmy.world
Xeon@lemmy.ml
IowaMan@lemmy.world
The_Vampire@lemmy.world
CatZoomies@lemmy.world
geosoco@kbin.social
Fudgeknuckles98@lemmy.world
BobaFett26@lemmy.world
100
Nice try Google (compuverse.uk)
submitted 1 year ago by Tibert@compuverse.uk to c/pcmasterrace@lemmy.world
88 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] ComeHereOrIHookYou@lemmy.world 0 points 1 year ago (1 children)

Performance wise widely depends on the site used. Some sites (notably Google ones) are notorious for implementing anti-competitive behavior, where if their website is visited other than a chromium based browser, it slows down or a functionality stops working.

I mean its the whole reason why Microsoft switch from Edge Edge HTML to Edge Chromium/Blink.

The only good reason right now if you want to stick with Chromium based browsers such as Brave is you're heavily into browser based games as currently Chromium (and it's older brother, webkit) are the ones that have the best webgl performance, Firefox can do it but not as fast as Chromium and performance impact is very noticeable

[–] bustrpoindextr@lemmy.world 0 points 1 year ago (1 children)

Some sites (notably Google ones) are notorious for implementing anti-competitive behavior, where if their website is visited other than a chromium based browser, it slows down or a functionality stops working.

I assume you're referring to Google meet (and the screen blur functionally), this is an open issue in Firefox for years, Google is using open standards to implement that, it's an issue in Firefox with how deadlocks work which is an extremely low level part of the browser. So it's not an easy solve.

There's a lot to complain about with Google, but this one isn't their fault. They use non-proprietary implementations and it's not their fault that Firefox will crash if they allowed Firefox users to use screen blur, the issue isn't a high priority for Mozilla.