this post was submitted on 28 Jun 2023
1704 points (99.3% liked)

PC Master Race

15005 readers
96 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
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 21 points 1 year ago (6 children)

That's a low-level Microsoft style move. Didn't thought Google will do it

[–] ZytaZiouZ 25 points 1 year ago (2 children)

Fun fact, aside from the annoying "this page is better in Chrome" messages on multiple Google sites, Google literally serves a totally different page to Firefox mobile users than mobile Chrome users. It's not a compatible issue, because of you take the user agent settings to claim it's Chrome, magically you get the full Google site. Also add much as I hate to reference Edge... it had significantly better performance on YouTube until magically it didn't anymore. It's almost as if Google purposely made competing browsers slower on their sites, when Edge and more recent Firefox releases work faster on non Google sites. Microsoft even gave up on the original Edge and just forked Chrome.

[–] Subverb 6 points 1 year ago

I use Google maps in a web app that my company has developed. Google maps is much slower in Firefox and Edge than Chrome. It's no accident.

[–] FeelzGoodMan420 0 points 1 year ago* (last edited 1 year ago) (1 children)

Yes. Youtube is slow as absolute fuck on Firefox, both mobile and desktop.

[–] ZytaZiouZ 3 points 1 year ago

That hasn't been my experience in many many years, but it was an issue at one time. It's possible that proper content filtering is making up for the difference in performance.

load more comments (3 replies)