Are you sure they're running the same set of tests? There's over 10000 tests in the full set that webpage runs, but there are subsets and fabrice might be running one of the subsets. FWIW test262 falls over partway through in Firefox and I have to kill the tab, though it doesn't crash. There are a bunch of test failures as well for things that are probably not implemented by anyone (I'm curious how many of the tests…
V8 has 89% coverage and QuickJS has 86%. https://test262.report/?date=2022-02-28
To add, QuickJS is almost completely comparable in test coverage, except for internationalization (which makes sense it wasn't a priority, since it's not used in a browser).
DDR5 prices would disagree with you. Plus, most laptop manufacturers rip you off for every RAM spec bump. $400 - $500 to go from 16GB to 32GB?! They can f--k right off! Not everyone is making six figure SV salaries to not flinch at these prices. That's why I love the framework laptop.
Imagine how expensive purchasing twice the battery from the manufacturer would be.
https://jsbench.github.io/#b39045cacae8d8c4a3ec044e538533dc Look at DOM performance. Chrome has a ceiling of about 45m ops/s where FF max speed is dependent upon your ram and bus speed reaching beyond 4-5b ops/s. In both though querySelectors perform at about the same speeds as slow as 25000 ops/s. I have written an OS GUI that executes in the browser. It loads, including full state restoration in about 120ms. I was…
> Despite all of this my biggest learning about performance is that mentioning performance during job interviews shows that you are incompatible with other JavaScript developers and will not be hired. As someone who done plenty of JS, cares about performance and also has handled hiring for JS positions in the past, I can tell you that this is generally not true. Caring about performance is not a reason to not get hir…
I have been doing web work for over 20 years. Everybody claims to care about performance, training, security, and so forth. The only thing that really matters in practice is comfort. Until developers are willing to abandon certain areas of comfort things like performance are only given lip service. In doesn’t matter what they want if they are actively working in opposition. This is performance is a massive incompatibility to hiring.
How do you know that isn't just measuring that most people keep to 5 tabs because otherwise everything grind to a halt. That's about how many tabs my wife's old Chromebook can handle before she has to start closing old tabs.
I am assuming it grind to a halt because it is CPU bound and not Memory bound? In that case the premises of CPU optimisations are not important would be, inaccurate? In reality it is complicated when we have extra CPU cycle to burn developers tends to put fancy new things. Which is basically what andy giveth bill taketh away.
It's because she runs out of memory and it starts swapping, I check the task monitor or whatever it is called in chrome. Some of the AdBlock extensions are taking up ram as well.
There are certainly lots of situations where one browser beats another For example in this microbenchmark, Chrome is 10x slower than both FF and Safari at one method. https://jsbenchit.org/?src=cfcb916dd03df45952183e6484a14344 Here's another where in one case Firefox is 54x faster than Chrome https://jsbenchit.org/?src=beb26575ad78caa99a2a8c45ce2b780f
https://jsbench.github.io/#b39045cacae8d8c4a3ec044e538533dc Look at DOM performance. Chrome has a ceiling of about 45m ops/s where FF max speed is dependent upon your ram and bus speed reaching beyond 4-5b ops/s. In both though querySelectors perform at about the same speeds as slow as 25000 ops/s. I have written an OS GUI that executes in the browser. It loads, including full state restoration in about 120ms. I was…
> "I was recently interviewing with a search engine company, one of the big ones, where I could demonstrate that JavaScript tool can execute file system search much faster than the OS and produce better results. They seemed really impressed."
How is this possible? OS should be using direct syscalls, any additional code you write should be pure overhead in theory, right?
> Despite all of this my biggest learning about performance is that mentioning performance during job interviews shows that you are incompatible with other JavaScript developers and will not be hired. As someone who done plenty of JS, cares about performance and also has handled hiring for JS positions in the past, I can tell you that this is generally not true. Caring about performance is not a reason to not get hir…
I have been doing web work for over 20 years. Everybody claims to care about performance, training, security, and so forth. The only thing that really matters in practice is comfort. Until developers are willing to abandon certain areas of comfort things like performance are only given lip service. In doesn’t matter what they want if they are actively working in opposition. This is performance is a massive incompatib…
> In doesn’t matter what they want if they are actively working in opposition. This is performance is a massive incompatibility to hiring.
No one is working towards degrading performance on purpose, and caring about performance is not "a massive incompatibility to hiring". But the fact that you keep stating this makes it clear that there seems to be plenty of other reasons organizations are not hiring you.
To which API are you referring? Mozilla, so far as I know, tries to protect the user.
Almost all web APIs can be used to fingerprint user (but Mozilla is reluctant to add new ones indeed when the ratio benefit/risk is too low). https://amiunique.org/
Lots of APIs are used to track users, but for example the Canvas API. Firefox also enables quite a few telemetry options by default.
My Speedometer results on an M1 Mac are: - Chrome v99: 204 - Safari: 266 How come I fall so far short of the post's advertised fastest-of-any-browser 300? Edit: Running in incognito got me a 251, so some of the slowdown must be from extensions. Edit 2: Seems like 1password and uBlock Origin decrease the score by around 30 each, I got a 276 with both disabled.
On my old fx8350 (overclocked) I get 60 in windows but 70 on linux with the same browser, Vivaldi. I wonder what the difference is.
I think that browser developers are optimizing the wrong thing. Specifically: they optimize for execution speed while they better optimize for minimum memory usage instead. Let me explain why this is more important. Let's say I am visiting a properly made website and it takes 10% of CPU to render. Even if browser devs make their browser twice faster, it will only save 5% of CPU time - and that would be completely unn…
Use tabsuspender for that. It saves memory by suspending the tabs which is not used for quite some time.
DDR5 prices would disagree with you. Plus, most laptop manufacturers rip you off for every RAM spec bump. $400 - $500 to go from 16GB to 32GB?! They can f--k right off! Not everyone is making six figure SV salaries to not flinch at these prices. That's why I love the framework laptop.
Imagine how expensive purchasing twice the battery from the manufacturer would be.
No need to imagine; we used to be able to buy a second battery before manufactures started gluing them in.