3 ms·

> But the three big public deprecations I'm aware of are Reader, Inbox, and G+. Google Code. Also Wave and half a dozen chat apps, but Code was a serious one t

by ebg13 8y ago

> But the three big public deprecations I'm aware of are Reader, Inbox, and G+. Google Code. Also Wave and half a dozen chat apps, but Code was a serious one that broke a lot of the developer web.

treis 8y ago
>Google Code. Also Wave and half a dozen chat apps, but Code was a serious one that broke a lot of the developer web. What did it break?
- Arnt 8y ago
  It hosted repos, and broke links to those repos and links within them. It also broke processes that relied on the repo, e.g. automatic issue creation in CI, but that's less serious. URLs that change without good reason are a PITA.
  - rrdharan 8y ago
    They have a process for setting up redirects. They also provide read only access to all public code AIUI: https://code.google.com/archive/about https://code.google.com/archive/about
    - ebg13 8y ago
      Setting up a redirect works if you are the administrator of the project...and are still alive. Migrating a project was simple if it didn't have a wiki. There are a lot of details that caused some real headaches. I remember it being like a mini Y2k at the time, and there's no telling how much we just collectively lost from it.
cdibona 8y ago
This is simply incorrect. As the person who (led? handled?) the shutdown/archiving, the vast majority of the 'developer' web had gone to github. The handful of active projects were given white glove treatment once we decided to shutter the site.
- ebg13 8y ago
  > the vast majority of the 'developer' web had gone to github I see hundreds of thousands of repositories on Github responding to the search "Automatically exported from code.google.com", which means they only transferred _after_ the shutdown was announced (when the export tool went live). Any wikis would have had to be hand-converted to not be broken, since the markup between the two systems was not compatible. I mean, thank you for handling it as well as it was handled, and thank you for (if you were part of that) the export tool, but let's not pretend that it wasn't disruptive.

by ebg13 8y ago

> But the three big public deprecations I'm aware of are Reader, Inbox, and G+. Google Code. Also Wave and half a dozen chat apps, but Code was a serious one that broke a lot of the developer web.

treis 8y ago

>Google Code. Also Wave and half a dozen chat apps, but Code was a serious one that broke a lot of the developer web. What did it break?

Arnt 8y ago
It hosted repos, and broke links to those repos and links within them. It also broke processes that relied on the repo, e.g. automatic issue creation in CI, but that's less serious. URLs that change without good reason are a PITA.
- rrdharan 8y ago
  They have a process for setting up redirects. They also provide read only access to all public code AIUI: https://code.google.com/archive/about https://code.google.com/archive/about
  - ebg13 8y ago
    Setting up a redirect works if you are the administrator of the project...and are still alive. Migrating a project was simple if it didn't have a wiki. There are a lot of details that caused some real headaches. I remember it being like a mini Y2k at the time, and there's no telling how much we just collectively lost from it.

cdibona 8y ago

This is simply incorrect. As the person who (led? handled?) the shutdown/archiving, the vast majority of the 'developer' web had gone to github. The handful of active projects were given white glove treatment once we decided to shutter the site.

ebg13 8y ago
> the vast majority of the 'developer' web had gone to github I see hundreds of thousands of repositories on Github responding to the search "Automatically exported from code.google.com", which means they only transferred _after_ the shutdown was announced (when the export tool went live). Any wikis would have had to be hand-converted to not be broken, since the markup between the two systems was not compatible. I mean, thank you for handling it as well as it was handled, and thank you for (if you were part of that) the export tool, but let's not pretend that it wasn't disruptive.