6 ms·

Gentlemen, I would like to interrupt this "google promotes open-source anti lock-in" PR party, and ask for a minute of silence for the recently departed GoogleC

• MikeKusold 10y ago
  When Google Code shutdown, people just needed to add another git remote and push their code up there. There wasn't any vendor lock-in there either. The Go community managed to migrate everything to GitHub without any real losses.
• johncolanduoni 10y ago
  Or maybe they shut it down because most project's pages had been voluntarily reduced to a link to GitHub? What about that explanation rings false?
• jpatokal 10y ago
  Um, Google Code was comprehensively obsoleted by Github. Google moved all their open source code to there, and provided a truckload of tools to help everybody else migrate to various other repos as well. http://google-opensource.blogspot.com.au/2015/03/farewell-to-google-code.html http://google-opensource.blogspot.com.au/2015/03/farewell-to...
• strcat 10y ago
  There's already an open standard for the core functionality of code hosting sites: Git. Projects migrate between GitHub, GitLab, Bitbucket and other alternatives all the time by simply changing the Git remote. There's some lock-in via extras like issue trackers and wikis but that's not difficult to migrate, especially with Markdown as a common standard so markup can be preserved. I'm not really sure why you think that's relevant to this. Google Code simply failed to compete with the alternatives and was obsoleted. It has nothing to do with lock-in.
  • deleted 10y ago
    [deleted]