71–80 of 183 posts
Desktop Firefox: 25
Desktop Chrome: 26
Laptop Firefox: 16
Laptop Chrome: 20
Laptop Safari: 21
Phone Firefox: 12
Phone Chrome: 10
---
Desktop: 5900X, 3090, Linux
Laptop: M1 Pro 14"
Phone: S24 Ultra
Ran all tests in private window to avoid extensions, and gave a minute to cool between tests. Laptop/phone was plugged in.
Earlier quoted context omitted.
I love the fact that an honest question is met with such hostility. I knew there was a quote, but was unable to think of it well enough for a proper search. It is easier to find an answer from other people with just a shard of detail that search engine will not find as there's no SEO for the broken fragment. I'm so happy to see this place is alive and well with the attitude to support a curious mind. What a tosser
So, why are you bringing up the quote in this context, then?
This is fantastic! Speedometer 1.0 was a breath of fresh air, and 2.0 was a much-needed refresh, but it's really been showing its age in recent years. 3.0 looks like a solid upgrade with many new kinds of sub-tests, contemporary frameworks, etc. I'm looking forward to sucking at this, and then slowly and systematically improving. :^)
Some of my results: Desktop Firefox: 25 Desktop Chrome: 26 Laptop Firefox: 16 Laptop Chrome: 20 Laptop Safari: 21 Phone Firefox: 12 Phone Chrome: 10 --- Desktop: 5900X, 3090, Linux Laptop: M1 Pro 14" Phone: S24 Ultra Ran all tests in private window to avoid extensions, and gave a minute to cool between tests. Laptop/phone was plugged in.
firefox 26.3
desktop: 7800xd3, 2060, linux
Earlier quoted context omitted.
[flagged]
Is it though? https://wpt.fyi/interop-2024
In my experience it's the buggiest browser out of the big three, and is often missing basic features like e.g.:
https://caniuse.com/?search=opus
Supported in Firefox for *12 years* now, in Chrome for 10, still no support in Safari.
They only "support" Opus audio in their special snowflake '.caf' container, which is super buggy and the last time I checked no open source program could even generate Opus '.caf' files that could be played by Safari on all Apple platforms. I ended up writing a custom converter which takes a standard '.opus' file and remuxes it on-the-fly (I only store '.opus' files on my server) into Safari-compatible '.caf' files, taking special care to massage it so that it avoids all of their demuxer/decoder bugs. You shouldn't have to do this to have cross-browser high quality audio!
On Firefox mobile I got a score of 3. So while Firefox is now super fast the performance of webapps might still be very bad on mobile. And I think this applies to all modern browsers: they are fast at rendering very slow webapps and websites.
Probably hardware dependent too as I get 8.11 on my fairly old Samsung S21. My newer laptop gets 14.9 so I'm not sure whether I agree performance is "very bad" on mobile -- it may be less performant but that is surely to be expected given the hardware constraints on mobile. YMMV.
Earlier quoted context omitted.
(I work on SpiderMonkey.) Benchmarking is hard. It is very easy to write a benchmark where improving your score does not improve real-world performance, and over time even a good benchmark will become less useful as the important improvements are all made. This V8 blog post about Octane is a good description of some of the issues: https://v8.dev/blog/retiring-octane Speedometer 3, in my experience, is the least bad b…
This doesn't say anything about what the scores mean. 21 is apparently better than 20, but how much better? You could say "1 better", tautologically, but how does that relate to the real world? Driving a car 1 mile per hour faster may be better, in a sense, but even if you drove 24 hours straight, it would only gain you 24 total miles, which is almost negligible on such a long trip. Nobody would be impressed by that…
Machine: AMD 5950X, 32GB RAM, 3080 GPU, Windows 11 Pro 23H2
Firefox v123.0.1 Edge v122.0.2365.80
EDIT: Interesting, I tried both in private windows later to bypass extensions, and Edge got 10.8 this time, Firefox got 16.9. I now have more questions.
Earlier quoted context omitted.
(I work on SpiderMonkey.) Benchmarking is hard. It is very easy to write a benchmark where improving your score does not improve real-world performance, and over time even a good benchmark will become less useful as the important improvements are all made. This V8 blog post about Octane is a good description of some of the issues: https://v8.dev/blog/retiring-octane Speedometer 3, in my experience, is the least bad b…
This doesn't say anything about what the scores mean. 21 is apparently better than 20, but how much better? You could say "1 better", tautologically, but how does that relate to the real world? Driving a car 1 mile per hour faster may be better, in a sense, but even if you drove 24 hours straight, it would only gain you 24 total miles, which is almost negligible on such a long trip. Nobody would be impressed by that…