> Chromium, you're buried under 50,000 layers of abstraction and the product of very complicated decisions and a massive build
As a webdev a few years ago, the Chromium team was oodles better than anyone else at delivering a reliable browser, and wayyyy better at fixing bugs than any other software team I have ever dealt with in my career (I just submitted bug reports to them, no direct or formal interaction). No idea what they are like now, but hotdamn that team was superlative. I hope it is enjoyable to work there, because the work output was phenomenal.
I never worked directly on Chromium, but I worked in its code base (for chromecast and google home products) and met many of the Waterloo folks who worked on Chrome. They were all top notch super smart people.
The codebase is huge. The code quality is on the whole excellent, but learning its ins and outs takes time.
As a webdev a few years ago, the Chromium team was oodles better than anyone else at delivering a reliable browser, and wayyyy better at fixing bugs than any other software team I have ever dealt with in my career (I just submitted bug reports to them, no direct or formal interaction). No idea what they are like now, but hotdamn that team was superlative. I hope it is enjoyable to work there, because the work output was phenomenal.