At this point, I think issue is not about products Google build, it is about how Google put their incentives in place. - Build new shiny thing -> promoted - Support shiny thing -> it's not difficult, everyone can do it This type of culture is influencing future direction of Google products, they put together awesome team, solve problem and get from 0 to 1, then team moves on, others don't have incentive to make 1 to…
I think this is both obsolete and subtly wrong. Big corps want products with global impact. When a product is new, it's evaluated for its potential. When it's been around for a while, it's evaluated on how well its growth is matching the estimated impact. Eventually, growth has stopped. If the product lands at an active base of a billion users or so, it's a success and people definitely can make a career out of maint…
Microsoft launched similar initiatives every time for decades even failing at prior tries. In the UI front they "play" with Silverlight, WFP, Windows Forms, MFC and a lot more. Try and retry.
I also think that these issues are worse when you are dealing with hardware: do they open the codebase to continue playing with the devices? I am on the European side of not only repairing youself but opening "dead" code or somethink like that. It is just an idea.