| "It didn't go away, though. It got archived and that archive is still up and running today. Those links you put all over the place should still be working." I think this is misrepresenting what the commenter stated. He appears to have stated the project hosting service "went away". This fits with the context of the OP which is comparing project hosting services, e.g., Google Code, Sourceforge, Github. If the context was software archives, e.g., software mirrors, instead of project hosting, then we could indeed claim "Google Code" still exists. However, the context is project hosting. And no one can upload new projects or revisions to Google Code anymore. Google Code project hosting did in fact "go away": https://codesite-archive.appspot.com/archive/about The old https://code.google.com/p/projectname URLs need to be redirected to https://code.google.com/p/archive/projectname Google then redirects these /archive URLs to storage.googleapis.com Too much indirection https://code.google.com/p/projectname becomes https://storage.googleapis.com/download/storage/v1/b/google-... Downloads https://storage.googleapis.com/download/storage/v1/b/google-... |
I'm going to defend Google on this. They don't need to maintain products forever but this case is a good way to shut down a service. Allow access to existing projects but make clear that active projects need to go somewhere else. The commenter can be upset that they can't use Google Code as a product but they shouldn't misrepresent the situation by saying the code is inaccessible. I checked a university project I created 15 years ago and it's still there. The commenter is objectively incorrect.
> Too much indirection
I don't think this is a valid criticism. The web is designed explicitly to do this. You can still access the code, that's good enough.