4 ms·

I wasn't explicit with my earlier comment, you're right about the beta period. I was referring to after when they exit beta and are a good, useful service for a

I wasn't explicit with my earlier comment, you're right about the beta period. I was referring to after when they exit beta and are a good, useful service for a year or two.

TheIronYuppie 11y ago
Disclosure: I work for Google. To the best of my recollection, I don't believe we've ever shutdown a product. Was there one in particular that hit you? (Reader, Wave, etc are totally different divisions.)
- rexignis 11y ago
  Google Drive hosting, to be fair it still works and you guys gave plenty of heads up (August 31, 2016). Just because they are in different divisions doesn't mean Google hasn't shut things down.
  - iso-8859-1 11y ago
    Source: https://support.google.com/drive/answer/2881970 https://support.google.com/drive/answer/2881970
- jrochkind1 11y ago
  Are the different divisions not Google? But it is more common for a Google product to be completely abandoned, no new features, few bugfixes, etc., as opposed to being actually shut down.
- toyg 11y ago
  Google Code was first turned into a graveyard, then deprecated, and soon will shut down altogether. Reader was not strictly a development tool (which is what I guess you refer to as "your division"), but was heavily used by developers, so it significantly disrupted people's workflow. Same for Wave and any web API (there's quite a few of them which were unceremoniously dumped).
  - KirinDave 11y ago
    It is not really Google's fault that Code was not a successful product, other than that they simply didn't have the energy/budget/will to actually make it a competitive product with Github.
    - toyg 11y ago
      Saying Google "doesn't have the budget" to do something is fairly preposterous, tbh. I can understand that they were wrong-footed by the rise of Github; Code was built to compete with Sourceforge, when GH didn't even exist. From day 1 though, it was clear that Code wasn't even "better enough" to actually kill SF for good; further development was incredibly slow. When Github hit their stride, Google reacted by just giving up. They didn't even attempt a comeback. So yeah, I think it's entirely their fault.
      - abiox 11y ago
        well, google isn't a small business, where "the budget" can be synonymous with "the bank account(s)". like many (all?) large businesss, things are organizationally regimented into units (and sub-units, etc), and budgets are allocated toward each unit. so while "google" might have funds, the "google code development team" may have a very tiny allocation.
        toyg 11y ago
        Of course, but budget allocation does not descend from Heaven fully formed, so to speak. Google directors (i.e. Google) decided Code was not a priority, so in the end it's Google-the-company's fault that it had to close.
      - jrochkind1 11y ago
        I think there was no reason for them to keep Google Code as a going concern with the rise of Github. They were not going to do as good a job as Github, and it wasn't something they were making any money off of. Even if they had been trying. But yes, like many Google products, it was basically released and abandoned. They weren't trying. (If they had been, maybe we never would have had a github...) I do think as a public service, they could have left all the code (and wiki documentation) accessible read-only virtually perpetually. Surely they can afford that. Instead, we get tarball download only, and only until late 2016, after which it's all gone forever, if it hasn't been migrated elsewhere by code owners or third parties.
- jlarocco 11y ago
  Oh brother. I guess if you're using the strict definition that a product is only something people pay for, then you may be right, but in the more generally accepted meaning that a Google product is something Google makes that people outside of Google use, you're just flat out wrong. There's a long, long list of Google products and services that have been discontinued, as somebody else already linked to in this thread: https://en.wikipedia.org/wiki/List_of_Google_products#Discontinued_products_and_services https://en.wikipedia.org/wiki/List_of_Google_products#Discon...
- TheIronYuppie 11y ago
  Crap. I literally meant to say "Google Cloud" and didn't. Yes, I'm well aware other products were shut down, but Google Cloud has not.
Klathmon 11y ago
Which would be understandable if they ever shut down any cloud service offering of this level before (which they have not). This whole "Google loves to shut stuff down" is really tired and overplayed. Go ahead and compare Google's track record with Apple's or Microsoft's, or any other company. They are about on par, yet Google almost always gives 6+ months notice (often over a year), provides one-click alternatives, allows you to export your data in one of many formats, and more often than not has an in-house alternative that you can use automatically. Take a look at the wiki page of google's products [1]. I'd be surprised if you even knew about 10% of those, let alone used more 1 or 2 significantly. [1] https://en.wikipedia.org/wiki/List_of_Google_products#Discontinued_in_2011 https://en.wikipedia.org/wiki/List_of_Google_products#Discon...
- rexignis 11y ago
  On that list that I've used: Buzz, Pack, Desktop, Reader, iGoogle. To Be Discontinued: Google Drive Hosting, Google Code. I don't think it's tired and overplayed. It's a consequence of how Google works; try lots of things and don't be afraid to pull the plug. That strategy is great, and it works. It's just sometimes the services that are on the edge of being worth Google's time to maintain cause the most backlash because a fair number of people used those services.
  - plonh 11y ago
    What to all those free consumer services that you don't pay for and and aren't connected to things you pay for have in common?
    - acdha 11y ago
      Google refused to allow you to pay for them? Each of those services could trivally have had some combination of ads and paid services but Google's management made strategic decisions to put resources elsewhere. Only using paid services up front might seem to help but one look at the way Google Apps has been in maintenance mode for years suggests that even that offers only limited protection.

I wasn't explicit with my earlier comment, you're right about the beta period. I was referring to after when they exit beta and are a good, useful service for a year or two.

TheIronYuppie 11y ago

Disclosure: I work for Google. To the best of my recollection, I don't believe we've ever shutdown a product. Was there one in particular that hit you? (Reader, Wave, etc are totally different divisions.)

rexignis 11y ago
Google Drive hosting, to be fair it still works and you guys gave plenty of heads up (August 31, 2016). Just because they are in different divisions doesn't mean Google hasn't shut things down.
- iso-8859-1 11y ago
  Source: https://support.google.com/drive/answer/2881970 https://support.google.com/drive/answer/2881970
jrochkind1 11y ago
Are the different divisions not Google? But it is more common for a Google product to be completely abandoned, no new features, few bugfixes, etc., as opposed to being actually shut down.
toyg 11y ago
Google Code was first turned into a graveyard, then deprecated, and soon will shut down altogether. Reader was not strictly a development tool (which is what I guess you refer to as "your division"), but was heavily used by developers, so it significantly disrupted people's workflow. Same for Wave and any web API (there's quite a few of them which were unceremoniously dumped).
- KirinDave 11y ago
  It is not really Google's fault that Code was not a successful product, other than that they simply didn't have the energy/budget/will to actually make it a competitive product with Github.
  - toyg 11y ago
    Saying Google "doesn't have the budget" to do something is fairly preposterous, tbh. I can understand that they were wrong-footed by the rise of Github; Code was built to compete with Sourceforge, when GH didn't even exist. From day 1 though, it was clear that Code wasn't even "better enough" to actually kill SF for good; further development was incredibly slow. When Github hit their stride, Google reacted by just giving up. They didn't even attempt a comeback. So yeah, I think it's entirely their fault.
    - abiox 11y ago
      well, google isn't a small business, where "the budget" can be synonymous with "the bank account(s)". like many (all?) large businesss, things are organizationally regimented into units (and sub-units, etc), and budgets are allocated toward each unit. so while "google" might have funds, the "google code development team" may have a very tiny allocation.
      - toyg 11y ago
        Of course, but budget allocation does not descend from Heaven fully formed, so to speak. Google directors (i.e. Google) decided Code was not a priority, so in the end it's Google-the-company's fault that it had to close.
    - jrochkind1 11y ago
      I think there was no reason for them to keep Google Code as a going concern with the rise of Github. They were not going to do as good a job as Github, and it wasn't something they were making any money off of. Even if they had been trying. But yes, like many Google products, it was basically released and abandoned. They weren't trying. (If they had been, maybe we never would have had a github...) I do think as a public service, they could have left all the code (and wiki documentation) accessible read-only virtually perpetually. Surely they can afford that. Instead, we get tarball download only, and only until late 2016, after which it's all gone forever, if it hasn't been migrated elsewhere by code owners or third parties.
jlarocco 11y ago
Oh brother. I guess if you're using the strict definition that a product is only something people pay for, then you may be right, but in the more generally accepted meaning that a Google product is something Google makes that people outside of Google use, you're just flat out wrong. There's a long, long list of Google products and services that have been discontinued, as somebody else already linked to in this thread: https://en.wikipedia.org/wiki/List_of_Google_products#Discontinued_products_and_services https://en.wikipedia.org/wiki/List_of_Google_products#Discon...
TheIronYuppie 11y ago
Crap. I literally meant to say "Google Cloud" and didn't. Yes, I'm well aware other products were shut down, but Google Cloud has not.

Klathmon 11y ago

Which would be understandable if they ever shut down any cloud service offering of this level before (which they have not). This whole "Google loves to shut stuff down" is really tired and overplayed. Go ahead and compare Google's track record with Apple's or Microsoft's, or any other company. They are about on par, yet Google almost always gives 6+ months notice (often over a year), provides one-click alternatives, allows you to export your data in one of many formats, and more often than not has an in-house alternative that you can use automatically. Take a look at the wiki page of google's products [1]. I'd be surprised if you even knew about 10% of those, let alone used more 1 or 2 significantly. [1] https://en.wikipedia.org/wiki/List_of_Google_products#Discontinued_in_2011 https://en.wikipedia.org/wiki/List_of_Google_products#Discon...

rexignis 11y ago
On that list that I've used: Buzz, Pack, Desktop, Reader, iGoogle. To Be Discontinued: Google Drive Hosting, Google Code. I don't think it's tired and overplayed. It's a consequence of how Google works; try lots of things and don't be afraid to pull the plug. That strategy is great, and it works. It's just sometimes the services that are on the edge of being worth Google's time to maintain cause the most backlash because a fair number of people used those services.
- plonh 11y ago
  What to all those free consumer services that you don't pay for and and aren't connected to things you pay for have in common?
  - acdha 11y ago
    Google refused to allow you to pay for them? Each of those services could trivally have had some combination of ads and paid services but Google's management made strategic decisions to put resources elsewhere. Only using paid services up front might seem to help but one look at the way Google Apps has been in maintenance mode for years suggests that even that offers only limited protection.