> So their manager asks them "Well, what is it you really want to work on? Maybe we can make it happen here and you don't have to leave all the perks of Google behind." The engineer says "I've always wanted to do OS development, and there's a bunch of neat research developments like capabilities that haven't yet been incorporated in a production OS." The manager says, "Hmm, I know of some guys over in this other department that have similar ideas. Why don't you connect with them and see if your interests align?"
What you describe is simply allowing a well-performing engineer to switch to new project, which of course happens all the time.
It's very different from "a bogus project for the sole purpose of retaining some engineers" that OP theorized.
> Google wins because it keeps these talented engineers off the market, and if the project succeeds they can win in a really big way.
So more or less like any ambitious new project? :)
> This is not unlimited, BTW.
Right, and again, goes against what OP was implying, that Google is going to run a huge project indefinitely just to retain a bunch of diva engineers who wouldn't work on anything else.
As I wrote above: "a rich employer may retain an unproductive employee for a limited amount of time if they expect it to ultimately pay off".
This is exactly what you are describing.
> if you were instrumental to the success of a project that made Google much more than you're ever likely to make in salary, you get one chance at a self-directed project.
Right, and Fuchsia is not a "self-directed project" of this kind. It's a big project with over 100 engineers, the vast majority of whom did not have the impact of Rob Pike or the others you mentioned.
Your comment is good and informative, but ultimately does not lend any support to the notion that Fuchsia really is some bogus project with no business case or future, solely for retention purposes, which is what OP was implying and what I am disputing.