Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bidding farewell to Google Code

google-opensource.blogspot.com

Post reply on HN
Print view View original

41–50 of 428 posts

Re: Bidding farewell to Google Code

#41

Post by daw___ »

pdknsk wrote: post #31

Does this mean Chromium is also moving away from Google Code? I'm curious how Google plans to migrate almost 500,000 bug reports. I'm expecting Google to purchase GitHub next in order to improve its deficiencies. In particular code search, which is really poor. Google Code search is good, so Google can then apply its search expertise "in-house". https://code.google.com/p/chromium/codesearch Maybe it's just habitual,…

I guess they will be using their own tool to migrate issues: IssueExporterTool

"How to export Google Code issue tracker data to other services" https://code.google.com/p/support-tools/wiki/IssueExporterTo...

Re: Bidding farewell to Google Code

#42

Post by lnanek2 »

pdknsk wrote: post #31

Does this mean Chromium is also moving away from Google Code? I'm curious how Google plans to migrate almost 500,000 bug reports. I'm expecting Google to purchase GitHub next in order to improve its deficiencies. In particular code search, which is really poor. Google Code search is good, so Google can then apply its search expertise "in-house". https://code.google.com/p/chromium/codesearch Maybe it's just habitual,…

At least for Android bug reports, Google mostly ignores them and closes them all as obsolete every release even though they weren't fixed. So I don't think they'll have any problem ditching Chromium bug reports. I've heard they have an internal bug tracker anyway, so the public ones like b.android.com are just jokes on people who don't know any better.

Re: Bidding farewell to Google Code

#44

Post by hackuser »

baggachipz wrote: post #14
hsgeyfjw wrote: post #4

Earlier quoted context omitted.

how do you (google) get away with being such asses? i know a bunch of developers will come to your defense, and say things like it is a free service, but it's not really, because for google, users are the product, and you guys have developed a rep for constantly shutting those users down. switching costs are very real, and people just don't trust you anymore. i don't care about google code in particular, but i hate g…

I might be feeding here, but the lesson is that you can't count on things Google releases to be around very long. Even APIs for popular products, like Google Maps. Just don't expect anything they release to have a long shelf life. It's annoying and it sucks, and it is now laughable when they tag things with phrases like "free code hosting forever" and so on. For them to change, they'd have to either: 1) Support every…

> Support everything into eternity

'Eternity' overstates it. Plenty of vendors support projects long after they are obsolete. IBM supported OS/2, released 1992 and a marketplace flop, until the end of 2006.

That means that if I need something to be around for awhile, I'll count on IBM and not Google. Google has the perogative to make that choice, of course, and long-term support generally is associated more with the business market than with consumers. Party that's because it costs more for businesses to change, partly IMO because consumers are poorly educated customers.

EDIT: It's a little odd to see this very normal comment modded down to -1 (now -3!). Another perfectly fine comment was modded down to 0. I don't care about the points at all, but it supports my instinct that some on HN are trying to protect Google. Employees? Fans?

Re: Bidding farewell to Google Code

#45

Post by jdmichal »

gtaylor wrote: post #20
baggachipz wrote: post #14

Earlier quoted context omitted.

I might be feeding here, but the lesson is that you can't count on things Google releases to be around very long. Even APIs for popular products, like Google Maps. Just don't expect anything they release to have a long shelf life. It's annoying and it sucks, and it is now laughable when they tag things with phrases like "free code hosting forever" and so on. For them to change, they'd have to either: 1) Support every…

They kind of get a bad rap for this because of how large and visible they are. The funny thing is that many of the people here on HN have worked on projects that had very finite lifetimes as well, often closing them down for some of the same reasons. Someone has to invest the time and money to keep services running, even if only limping along. Google likes to experiment and test the waters. It's part of why they've b…

I also find a certain level of humor in the oft-espoused "release and pivot" ideology, accompanied with the pleas for mercy found in these Google product shutdown threads. What is different? Why is Google not supposed to release and pivot like everyone else?

Re: Bidding farewell to Google Code

#46

Post by pbreit »

gtaylor wrote: post #9
hsgeyfjw wrote: post #4

Earlier quoted context omitted.

how do you (google) get away with being such asses? i know a bunch of developers will come to your defense, and say things like it is a free service, but it's not really, because for google, users are the product, and you guys have developed a rep for constantly shutting those users down. switching costs are very real, and people just don't trust you anymore. i don't care about google code in particular, but i hate g…

Edit: The parent comment was flagkilled, but he was ranting about how Google should be expected to keep Google Code (and their other failed services) on life support indefinitely out of the kindness of their heart, because negative public perception. This is pretty ridiculous. It is a free service, sustained only by how long corporate wants to foot the bill. This is why it's so important to keep in mind how sustainab…

I don't think "free" has anything to do with it. In fact, the reason this is not a big deal is specifically because there exist at least 2 superior free options.

Re: Bidding farewell to Google Code

#47

Post by mike_hearn »

daw___ wrote: post #41
pdknsk wrote: post #31

Does this mean Chromium is also moving away from Google Code? I'm curious how Google plans to migrate almost 500,000 bug reports. I'm expecting Google to purchase GitHub next in order to improve its deficiencies. In particular code search, which is really poor. Google Code search is good, so Google can then apply its search expertise "in-house". https://code.google.com/p/chromium/codesearch Maybe it's just habitual,…

I guess they will be using their own tool to migrate issues: IssueExporterTool "How to export Google Code issue tracker data to other services" https://code.google.com/p/support-tools/wiki/IssueExporterTo...

The problem is that last time I looked at these tools, they all sucked. I migrated code hosting and website for my project to github but left issue tracking on Google Code because the github API doesn't let you do any kind of high fidelity import of issues. I hope GH find a way to do some kind of reasonable issue import soon.

Re: Bidding farewell to Google Code

#48

Post by gtaylor »

jdmichal wrote: post #45
gtaylor wrote: post #20

Earlier quoted context omitted.

They kind of get a bad rap for this because of how large and visible they are. The funny thing is that many of the people here on HN have worked on projects that had very finite lifetimes as well, often closing them down for some of the same reasons. Someone has to invest the time and money to keep services running, even if only limping along. Google likes to experiment and test the waters. It's part of why they've b…

I also find a certain level of humor in the oft-espoused "release and pivot" ideology, accompanied with the pleas for mercy found in these Google product shutdown threads. What is different? Why is Google not supposed to release and pivot like everyone else?

It is puzzling, but I think their rapid ascension has led to some people setting their expectations for Google too high. Others seem to hold them to some golden moral standard (of their own design), for some reason.

In the end, they are a for-profit business. Not a charity.

Re: Bidding farewell to Google Code

#49

Post by mherdeg »

cdibona wrote: post #2

Hi everyone. I wanted to let you know (and I know this isn't a huge surprise) that we will be shutting down the Google Code project hosting system over the next year. Wired did a nice story about Github that touches on the shutdown: http://www.wired.com/2015/03/github-conquered-google-microso... I'll be hanging around answering questions, but the short form of 'why' is that it just isn't used much anymore, ourselves…

It sounds like Google hasn't committed to serving this content in any form past 2016.

But there is a plan to provide archival-style info throughout 2016 (tarballs per project). Is Google in touch with someone like the Intenet Archive to make sure that these data are still available after Google stops hosting them? I'm sure there's some group that's willing to take on the work of hosting the project metadata and associated files.

I personally, occasionally use a handful of "orphaned" libraries that haven't been touched in years and only live on Google Code. Gonna be a bummer when those links break.

Re: Bidding farewell to Google Code

#50

Post by samatman »

cdibona wrote: post #10
gtaylor wrote: post #5

I'm sure some are going to immediately say "Yet another Google casualty", but I feel like this one probably needed to happen. It's been stagnant for years, and they have been on the mindshare decline since the first two years. I dread having to deal with open source software that is still on Google Code. Admit failure, provide plenty of notice (like they're doing), and close up shop so resources can be spent on more…

Basically, this. In case others didn't read the post, you'll have almost a year to take your projects off. We wanted the handful of projects that were still active to have plenty of time to migrate.

Is it possible, when code goes cold, to redirect URLS to archive.org rather than 404ing them?

I have been known to make use of ancient, forgotten code from geocities pages, and keeping the integrity of hyperlinks together matters to me. Think of the blog posts that currently link to Google Code pages; those will never be updated.

Post reply on HN