3 ms·
Honestly, while it makes sense to shut down Google Code, it is mindboggling that Google destroys information. Public projects on Google Code ought to be archive
by cpks 12y ago
Honestly, while it makes sense to shut down Google Code, it is mindboggling that Google destroys information. Public projects on Google Code ought to be archived and the archives and redirects ought to be kept up in perpetuity. People may not be reached by the announcements. Some projects, the authors may be dead, in a coma, etc. Some may just not care.
This is the #1 reason I fear the cloud. When Google shuts a project down, unless you act fast, you lose data.
Would it be rocket science for Google to set up a service which provides:
1. DNS hosting
2. Static page redirects
3. Static page hosting
4. Secure static page hosting (available only to authenticated accounts)
in perpetuity? This would be a read/delete-only service.
When Google Reader shuts down, I could access my data forever. When Google Code shut down, the project archives would stay up as read-only. Etc. No maintenance, and a one-time migration with Google Takeout for each dying service.