Thought I’d never see the day when Firefox would match Chrome on Speedometer.
There’s also a few other benchmarks got a sizable boost. https://arewefastyet.com/
Thought I’d never see the day when Firefox would match Chrome on Speedometer.
There’s also a few other benchmarks got a sizable boost. https://arewefastyet.com/
@Molecular0079 I think we won’t get much farther than this.
I disagree. Engineering requires subjective feelings too, depending on what is being engineered off course. But that’s going too far now. My points are still valid and your replies are confirming, such as you feel a difference (you did not measure it, you feel see it), and I do not. That’s my point.
Engineering uses objective measurements and techniques to work towards a certain subjective feeling, but that’s the extent of where subjective feelings matter.
No, your point was that synthetic benchmarks are just synthetic and do not matter in reality. My point is that synthetic benchmarks matter a lot in some usecases, particularly in high performance oriented ones. These two statements are not the same, regardless of how many times you say they are.
@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.