4 ms·
> Firefox easily beating Chrome in this decade-old JavaScript benchmark while also > Meanwhile for the newer and more demanding JetStream 2.0 benchmark, Googl
by vorticalbox 3y ago
> Firefox easily beating Chrome in this decade-old JavaScript benchmark
while also
> Meanwhile for the newer and more demanding JetStream 2.0 benchmark, Google Chrome continues to win easily over Firefox
- baliex 3y agoBig firefox fan here and it's kinda sad to read that
- fabrice_d 3y agofwiw, https://arewefastyet.com/win10/benchmarks/overview?numDays=60 https://arewefastyet.com/win10/benchmarks/overview?numDays=6... tracks a number of benchmarks.
- agumonkey 3y agoI wouldn't, firefox has less resources and faced an uphill battle for years. The fact that they keep improving regularly and significantly, even though late on some front is applaud worthy to me.
- insanitybit 3y agoCan someone tell me how much Chrome has in terms of resources? Firefox, a company with one main product, has hundreds of millions of dollars coming in + millions in donations. That should pay for a sizeable engineering team. Is the Chrome engineering team much larger? Is the V8 team larger than the SpiderMonkey team, significantly so?
- tristan957 3y agoDonations don't pay for Firefox development. Chromium is a bit more than Google these days. Mozilla's largest failure to date has been their inability to attract other significant corporate interest, which Google has done with Chromium
- londons_explore 3y agoDrawing a precise boundary around "Chrome" is hard, since many people work on it part time, or are associated with tangentially related projects, like the skia graphics engine, v8 javascript engine, etc. However, there were 767 unique authors who committed code direct to chromium in the last week: https://github.com/chromium/chromium/pulse https://github.com/chromium/chromium/pulse And I would guess the Chrome team is probably 3-5x that, since many people may not be working on code, may not commit directly, or might be working on big things on branches and didn't commit anything this week. Also, that doesn't count work on external dependencies, which are counted as "autoroll bots".
- londons_explore 3y ago3000 engineers * $200k average total comp = $600M. It's in the same ballpark as mozilla's total revenues.
- smarnach 3y agoAverage total comp for an FAANG engineer in the US is more like $450k, and last time I heard numbers, Chrome and adjacent teams were more like 4,000 people.
- londons_explore 3y agoI guess Mozilla engineers are paid quite a bit less. They hire the people with a conscience, so don't need to pay the 'do evil' salary premium...
- astrange 3y agoWhich average is that? Don't think it's median W2 income.
- tick_tock_tick 3y agoYeah it seems a touch low. I'm not at one of the big boys and $200k is more like base salary then total comp. RSUs show up on a W2.
- tomashubelbauer 3y agoUnfortunately the money for within Mozilla is not that straightforward in favor of Firefox and I imagine I am not the only Firefox user who is incredibly annoyed with that. I'd rather send money to individual devs' Github Sponsors sounds than give Mozilla a donation the devs will never see a cent of.
- dblohm7 3y agoOptimizing for benchmarks tends to not work all that well for real-world sites. I wouldn't worry about it.
- yborg 3y agoAnd on macOS, Safari beats the pants off of Chrome by an even larger margin.
- culi 3y agoSafari only has to worry about one OS. Not just one OS but also a single line of hardware. Very easy to optimize for. It's why iPhones have tiny batteries compared to their competitors but still deliver competitive, and usually superior, battery life
- deleted 3y ago[deleted]