Firefox
The latest news and developments on Firefox and Mozilla, a global non-profit that strives to promote openness, innovation and opportunity on the web.
You can subscribe to this community from any Kbin or Lemmy instance:
Related
- Firefox Customs: [email protected]
- Thunderbird: [email protected]
Rules
While we are not an official Mozilla community, we have adopted the Mozilla Community Participation Guidelines as far as it can be applied to a bin.
Rules
-
Always be civil and respectful
Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity. -
Don't be a bigot
No form of bigotry will be tolerated. -
Don't post security compromising suggestions
If you do, include an obvious and clear warning. -
Don't post conspiracy theories
Especially ones about nefarious intentions or funding. If you're concerned: Ask. Please don’t fuel conspiracy thinking here. Don’t try to spread FUD, especially against reliable privacy-enhancing software. Extraordinary claims require extraordinary evidence. Show credible sources. -
Don't accuse others of shilling
Send honest concerns to the moderators and/or admins, and we will investigate. -
Do not remove your help posts after they receive replies
Half the point of asking questions in a public sub is so that everyone can benefit from the answers—which is impossible if you go deleting everything behind yourself once you've gotten yours.
view the rest of the comments
@Molecular0079 You are wrong. Synthetic benchmarks do not represent the normal daily usage of users. I did not say the results are wrong and could not help in finding slow parts. But they are not indicative to what browser is faster than the other, because no single benchmark can answer than question. I think you don't get what I'm saying here. As I said, I think we won't get much farther than this. My statements are all correct.
The "synthetic benchmark" that OP mentions is simply a to-do list app written using different web frameworks, populated with some Todo items and then reloaded. This is done many times and then measured. I don't know about you, but this seems pretty real world usecase to me.
Of course not, but a sum of many of what you call "synthetic" benchmarks will give an indication of which browser is faster.