this post was submitted on 18 Sep 2024
397 points (94.4% liked)
memes
10322 readers
1932 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
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
Firefox objectively has poor responsiveness in some apps, hence why some "works only in chrome" banners are justified. Can't quite put my finger of it, but it got a lot worse somewhere between quantum and heartbleed(but not because of it, I checked), and it never recovered. In my own projects that were time-sensitive, like 3d games and music apps, I couldn't find the source of it, but found that while some approaches led to major performance hit on firefox, others majorly hit chromium, and vice versa, and it was all about juggling to finding an approach that doesn't hit either as hard. But in some cases there were none and so I had to choose. Obviously the browser engine with a higher market share wins. And because of that, to be on par with Chrome, Firefox not only has to be better, it has to be not worse in all cases, which is a rather tough challenge.