Earlier quoted context omitted.
I work at Google so my perspective is to be biased, but that's not what I see. I work on infrastructure, and so a few years back, when I proposed a major project, I had to demonstrate how it would save *many* times the fully loaded cost of the engineers on the team, by reducing the Storage TCO for all of Google (for example). It was not enough for the project to "break even" --- the benefits had to do more than just…
As so many people learned over the years in storage org, essential modus operandi was “just do your current shit, this new shit you are proposing is too hard and we don’t want to do it”. I lost count of improvement proposals that ultimately were not getting supported (there was a funny one with (first) hosted NFS prototype, when they tried to turn it off, turned out there were pissed-off customers running business wo…
[1] https://blog.google/products/google-cloud/dynamic-hybrid-smr...
[2] https://www.t10.org/pipermail/t10/2018-September/018566.html
On the production kernel team, colleagues of mine worked on some really cool and new shit: ghOSt, which delegates scheduling decisions to userspace in a highly efficient manner[3]. It was published in SOSP 2021/SIGOPS [4][5], so peer reviewers thought it was a pretty big deal. I wasn't involved in it, but I'm in awe this cool new work that my peers in the prodkernel team created, all of which was not only described in detail in peer-reviewed papers, but also published as Open Source.
[3] https://research.google/pubs/pub50833/
[4] https://www.youtube.com/watch?v=j4ABe4dsbIY
[5] https://dl.acm.org/doi/10.1145/3477132.3483542
We have some really top-notch engineers in our production kernel team, and I'm very proud to be part of an organization has this kind of talent.