this post was submitted on 17 Oct 2024
663 points (97.6% liked)
Technology
59422 readers
2942 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is part of Googles strategy. Ever since the Chromium engine took off enough and everyone else fell behind they began introducing more and more changes that merely benefits them, with less public debate or proper communication (or even adherence to common standards). Last thing I remember, aside of manifest v3, was them killing off JPEG XL as it was a competitor to webp and webm (which they control). JPEG XL was actively worked on and would've probably turned out better before they killed it without any previous notice.
Given Googles dominant market position, their influence and everyone wanting to cut corners wherever possible sometimes Firefox support is just ignored.
tl;dr It's not Firefox' fault. It's Google's sabotage.
Ah I see, it sounds like I'm saying it's Firefox fault. No I definitely agree, chromium is the largest market share, and gets the most support, and doesn't always follow standards, so some websites will have compatibility issues if they don't specifically focus on Firefox support.
It's just a sucky situation.