This has two logistical consequences: 1 - it's more valuable to launch a new product that it is to successfully maintain/grow a current one. 2 - the person running these new projects tends to get promoted away, leaving it rudderless.
Google could change all this overnight by restructuring what these review boards prioritize.
This is very stale information at this point. Product launches are now pretty heavily gated, and promotion criteria are far less based on launches than on overall impact, including but not limited to improving/maintaining products.
(Googler but interpretation is my own)
(Also a Googler.)
If you don't believe it, try selecting 10 of their supposedly killed products at random. Had you honestly heard of them ever before? Do they look like something that would have had a significant user base? Hell, do they even look like they were actual products?
So, two things:
1) Changing culture is really hard, especially at a company the size of Google, and
2) Even if they could change the culture, it's possible they simply don't care or they believe the benefits outweigh the cost.
Always building new infrastructure, and not maintaining the existing one.
"Zircon is the core platform that powers Fuchsia. Zircon is composed of a kernel (source in /zircon/kernel) as well as a small set of userspace services, drivers, and libraries (source in /zircon/system/) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation."
- Fuchsia Docs, https://fuchsia.dev/fuchsia-src/concepts/kernel
Sometimes they stumble upon something another PA needs, but often it just ends up as a patent or research paper.
Guido van Rossum (creator of Python) is a Distinguished Engineer at Microsoft. Before that, he worked at Dropbox.
I get the quarterly check-ins from the "alumni recruiting" team, and can assume Guido does too.
Who can divert from Google's massive ad income funnel?
Apple.
Facebook.
(Also maybe several foreign governments' antitrust cases.)
An engineer on your payroll is an engineer not on the competition's payroll.
Look no further than you're being _upvoted_ for quintupling down on inanity completely divorced from the article that's we're supposed to be discussing, even with schoolyard debate nonsense like "can you name even one thing backing up your thesis statement?" (back in the day, or still with more traditional HN posts, you'd get something more like: 'I find that surprising, what makes you feel that way?'. Dang calls this "coming with curiosity" or something like that)
Meanwhile in the sibling thread, we have a guy with a year old account neener-neering me for daring to mention things are bad because it's a noob fallacy, and people who have actually been here a while getting flagged/dead through the floor for pointing out this _isn't actually some steadfast rule_, its a classic HN "rule". Meanwhile, I've been here for 12+ years and its never been close to being as bad as it is right now.
This site, and you, are getting what always happens to these sites: too large of an audience to preserve quality of discussion over group dynamics. You shall inherit the board, but, no one will be the wiser for you being here - it's all half-baked assertions, schoolyard bully absolutist nonsense that you know isn't argumentation, you'd never talk like that to someone in real life. Then add the thesis here being that people _in the actual company_ aren't seeing the truth, their coworkers are engaged on makework PhD bullshit because otherwise they'd jump to Apple (never mind that the #1, #2, and #3 pieces of career advice in the valley is to leave so you get promoted)
As for your "coming with curiosity" scolding attempt? Please review the first two words of my comment.