3 ms·
> It's very different from "a bogus project for the sole purpose of retaining some engineers" that OP theorized. I mean, it's not like Google is inventing bogu
by derefr 8y ago
> It's very different from "a bogus project for the sole purpose of retaining some engineers" that OP theorized.
I mean, it's not like Google is inventing bogus projects in a top-down sense, with some middle-manager somewhere coming up with "private works projects" and staffing them with engineers Google wants to keep. Nobody is claiming that.
No, what the GP was proposing is that the projects are bogus in a bottom-up sense: they're projects that are entirely useless to Google's shareholders in both a short-term and long-term sense, but which the engineers really want to work on, and which at least aren't actively harming Google (or perhaps they are, but not as much as Google would be harmed if the same project were developed in the wild.) This is very different from "basic research" (Google X et al), which is useless in a short-term sense, but may yield large positive returns later on. These projects are bogus because the best-case scenario for them is no net effect on Google as a business. (They might have quite an effect on the the world, but if there's no way for Google to convert that effect into shareholder value: bogus.)
Fuchsia is a perfect case: at best, it replaces Android, for no net benefit to Google (since they already dominate the mobile ecosystem with Android.) But if the engineers working on Fuchsia couldn't work on it at Google, they'd have started a similar project outside Google... and then Google would be in the position of a non-Google-owned OS displacing Android's share of the mobile-OS market.
Much better that these engineers do something useless [from a business perspective] that merely keeps stable Google's share of a market, than that they do something that actively lowers Google's share of a market.
- nostrademons 8y agoOr more that they're likely useless from a shareholder perspective, but have a small chance of paying off in a large way, and worst-case keep the engineers occupied & employed at the company. Google doesn't generally allow projects that everyone knows have zero chance of being useful in a bottom-line sense; you can't, for example, build a D&D campaign index on company time even if you're T9. (There was a big debate over this near the tail end of the Eric Schmidt years, when you actually could, and this was one reason for Larry's "More wood behind fewer arrows" campaign.) But for something with a small chance of having a large impact, like a new OS or programming language or attempt to speed up scientific progress? Google can totally get behind that, because worst-case, you keep the engineers employed and available for future use, while best-case, you've got a computer science breakthrough. Fuchsia fits right into this case, as does Dart and Go and Unladen Swallow and several other projects.