Assuming that Chrome team have thousands of engineers, designers and PMs (which is a pretty reasonable number as a modern browser is comparable to OS), I expect them to spend more than a billion each year. Mozilla is really in short of resources.
Like who for instance? Basically only Blink, WebKit and Gecko are usable non-toy web engines these days, and they're all backed by big companies with deep pockets and many engineers.
Opera's long gone, now it's a chromium fork. Internet Explorer is gone, now MS uses a chromium fork. The hype new browsers like Brave and Vivaldi are just chromium under the hood.
It's like the difference between making a Linux distro and maintaining a full OS.
My reasoning is that Google's investment is massive and just because they're throwing money and people at a problem doesn't make it necessary for everyone else to do so as well.
Just writing a javascript runtime alone isn't just a "handful of engineers." WebGL stack? WebRTC? Layout engine/compositor? Notifications? You're kidding me, there is no small team in the world that could ship a browser stack end to end.
WebKit is a bad example, considering the KHTML history alone. These things don't just take devpower, but time - consider, for example, this: http://www.ekioh.com/flow
From what I understand, that team is relatively small in comparison, but actually does have this widely-ish deployed. So it theoretically could be done with less... but it's still insane to even consider. This isn't simple, and anyone who's trying to imply otherwise is wrong.
The other commentator you're responding with also never discloses they worked with Apple previously, while pretty much endlessly pumping up their work here. shrug
I was aware of Ekioh, but only tangentially; I had no idea of their progress so I didn't bring it up. I'd say it's great that they've managed to come this far. And to clarify if it wasn't plain from my other comments, I think that Chrome is the exception rather than the rule: it's an absolutely massive team. Possibly the largest of all the browser vendors that can make something close to compatible with the modern web. When pressed for an example I mentioned WebKit because just happened to be the by far the best example: it's the one that I could point to as competing with Gecko or Blink, plus it had a nice webpage I could link to instead of making people comb through Git commits.
> You're kidding me, there is no small team in the world that could ship a browser stack end to end.
https://webkit.org/team/, ⌘F "Apple". Balance the people on that list who have left or are assigned to work on something else with those who aren't listed there.
And almost all of them gave up developing their own engine except Apple and Mozilla?
FYI, WebKit itself takes hundred of engineers from Apple (which would be roughly similar to Blink). And this is only for the rendering engine, which is pretty small compared to the entire browser codebase. Thus Apple is investing a comparable amount of engineering resource into Safari. Where are "Other browsers"?
Please don't assert this so lightly unless you have any evidence to support it. A rendering engine is just a tiny fraction and you gotta take care of literally thousands of other components to build a modern browser. This applies to Chrome, Firefox and even old good IE. I don't expect any valid reasons why the same logic cannot apply to Safari.
The number above is probably pretty close, but there's a misconception that WebKit is only a tiny fraction of Safari: it's not. Most of the manpower and work goes into it; Safari is just chrome around it (albeit chrome that does take a reasonable amount of work to make…just not as much as it does to support JavaScript and WebAssembly VMs, page styling, rendering, WebGL and WebGPU, networking, tracking prevention, and maintaining support for the the ever-growing list of web standards WebKit supports and participating in discussions on shaping them). Safari is just one of the clients of WebKit.
Google employs thousands of engineers who spend a majority of their time thinking about Google Chrome. This gets slightly more complicated because of, e.g., the strategic impact of Chrome in other places like ChromeOS. The right comparison would be Apple's WebKit and Safari teams.
to get one year's worth of commits as of today (as of rev c43e247d6444 to be exact), I get 1250. If I repeat that with "google.com" instead of "chromium.org", I get 623. So figure ~1800-1900 there.
I get 15. If I repeat that with apple.com instead of webkit.org I get 70. If I just list all distinct authors, I get 128. Note that this is an underestimate of what it takes to build a browser, because a bunch of the parts of an actual browser are not in the webkit repo itself last I checked. Like the whole network stack.
I get 359. I am quite sure this last is is an underestimate: I am a Mozilla employee, but I use a non-mozilla.com address in my commits, because I started contributing before becoming an employee. I'm not the only one. The total number of distinct committers there is 1497 which is a serious overestimate: web platform test changesets come with their original author, who is often an engineer working on some other browser. If I filter out webkit.org, microsoft.com, google.com, chromium.org, webkit.org, that leaves me with 1265. This is almost certainly a significant over-estimate, since it's more than the total number of Mozilla employees.
Note that we may be undercounting QA here, since not all of them might commit to the main repository.
On the other hand, we might be counting one-off contributors who are not really on the "browser team" per se, especially for "apple.com" and "google.com". We're also overcounting somewhat depending on how much churn there was over the course of the year (people leaving, new ones joining).
But pallpark, I suspect an unrealistic lower bound is 100 and a reasonable lower bound is 150-500, depending on how much of the tech stack you want to delegate to other entities. The Chrome team is a lot bigger than any of those numbers, of course.
With 50 or so devs (let's forget for this example about managers, UX researchers and designers, HR, etc.) you'll get maybe a JavaScript VM and a small UX.
Not nearly a browser :(
> Around 60-80 people judging from the names listed under the various Blink teams (Rendering, DOM, Memory, Style, etc).
That sounds like a really, really vast underestimation. To the best of my recollection Chromium embedding teams inside Google that are 30+ developers (again, let's forget managers, UX researchers, etc.). I know that there are at least 4 such teams at Google.
I would be very surprised if Google didn't have at least 1000 developers working on Chromium.
>With 50 or so devs (let's forget for this example about managers, UX researchers and designers, HR, etc.) you'll get maybe a JavaScript VM and a small UX.
Not so sure. I remember the Webkit guys being a very small team (and they basically did the whole of Safari). There was some such mention on Dave Hyatt's blog at some point.
And, as far as the "chrome" part (UI, settings, etc) goes, wasn't Firefox at first the work of a couple of people, who forked their own UI version of Mozilla? And still it got to be the most popular browser at the time.
Not to mention how whole OSes and other challenging things have been done by smaller teams...
> With 50 or so devs (let's forget for this example about managers, UX researchers and designers, HR, etc.) you'll get maybe a JavaScript VM and a small UX.
Safari does those two specific things with a quarter of the number you mentioned. The entire team is nowhere near a thousand people.
WebKit runs on macOS, iOS, iPadOS and watchOS across Intel and ARM architectures.
WebKit provides the web views for countless 3rd party apps, including Mail, Calendar, iTunes, etc.
Apple certainly has fewer people who get paid to write code for Safari/WebKit than Google has on Chrome/Blink. I wouldn’t be surprised if Mozilla has more people too, especially since they’re rewriting pieces of the browser engine at the same time.
This list has 400 pages of contributors (~8000 people). Even with a very conservative assumption in that only 10% of them are full time developers, it's still 800. This doesn't even include other derivative projects and non engineers.
