Live data from Hacker News

Bidding farewell to Google Code

google-opensource.blogspot.com

221–230 of 428 posts

Re: Bidding farewell to Google Code

#221

Earlier quoted context omitted.

How is this even a failure? Google Code was the best at what it did for several years. Now it's not. That doesn't eradicate the time in the past where it provided real value to millions of users. A party isn't a failure just because everyone eventually has to go home. It just means even successful things have ends.

> How is this even a failure? Google Code was the best at what it did for several years. Google Code had a few good years, and I am grateful that it happened. However, it did fail to win the software forge battle as the space heated up. It failed to evolve enough to keep up. It failed to keep the mindshare it built in those two initial years as Github and others blew past it over the next six. So call it for what it…

> However, it did fail to win the software forge battle as the space heated up.

This is just the wrong metaphor entirely. It's not a battle because battles, and even wars, have ends.

But you're implying that somehow today is special and marks the end of the battle and therefore GitHub "won" because it's the most popular right now. But will it be in twenty years? If not, will you have to go back and edit your comment?

There's no winning and losing here. It's just an endless continuum of time where popularity waxes and wanes, where things end and new things begin. Google Code had a good run. So did SourceForge before it, and CVS and FTP sites before that. Something will come along to replace GitHub eventually.

The computer world is new enough that we haven't gotten used to the idea of software technology having a finite lifespan, but it absolutely does. That's OK. The goal of every product on Earth doesn't have to be to live forever.

Re: Bidding farewell to Google Code

#224
post #208
post #196

Earlier quoted context omitted.

Google hates anything that requires a human's touch, and per the article: > Lately, the administrative load has consisted almost exclusively of abuse management. They see Google Code as a time-sink, and they're probably right, and it's not surprising to me that they'd drop something that is no longer serving it's intended purpose, but instead has negative implications for their model. Keeping it going forward would r…

> I work on Google Code, and we will be putting a service in place to redirect deep links to project homepages, issues, etc. to their new locations. And this is an opt in service, nothing is automated. They could ,AT LEAST, partner with Github or someone else to have the whole thing automated... Seriously... the really want to put 0 money in that stuff,they don't give a damn. There are seriously good projects that wi…

I seriously doubt Github would ever agree to that automation. First, what accounts would all these orphan repos go under? Second, how much spam would they be agreeing to host by saying yes to that?

This is a much better job for The Internet Archive or a read-only google code in perpetuity.

edit: in fact, it looks like they're planning on making a read-only version, but the definition of "legitimate" is going to be very important to nail down:

> cdibona: We are planing on taking the majority of these legitimate, open source, 'abandonded' projects and putting them up in cold storage in a git repo on googlesource.com

https://news.ycombinator.com/item?id=9192554

Re: Bidding farewell to Google Code

#225
Hi, Sebastian from RhodeCode here. We do a fully-featured, behind-the-firewall SCM for Git, Mercurial and SVN - used by some of the world's largest organizations and also some well known Silicon Valley startups.

If you want to host your source code on your own (virtual) server then please contact us at https://rhodecode.com and mention Google Code - we are giving away free licenses for startups and smaller teams.

Re: Bidding farewell to Google Code

#226

Earlier quoted context omitted.

It is a very nice system, but the stuff that goes into a shutdown had me fighting to keep the message as tight as possible. I wanted to go on about Bitbucket, gitlab, and put in a long discussion about how this doesn't effect the scalable git team at google at all (we host android and chrome and a ton of internal teams on a git backed on our backends here) , but had to keep the message pure... But I heartily recommen…

Rather than recommending a specific Git hoster such as Github, you should have listed out alternatives... especially as Google Code also supports Subversion and Mercurial.

Subversion & Mercurial? Then actually just RhodeCode (https://rhodecode.com) is the only alternative since it supports Git, Mercurial and Subversion.

Disclaimer: I am RhodeCode's co-founder.

Re: Bidding farewell to Google Code

#227
post #210

Earlier quoted context omitted.

Well for me personally I always head straight to the pricing page of any service I'm interested in and I didn't see any mention of the repository hosting you do there. Is that just for support / enterprise installations? Might be helpful to mention it there. But beyond that I dunno.

It is mentioned there but pretty low on the page, "Sign up for our free GitLab.com service if you want to use GitLab without installing it.". What do you think?

Ah I saw that but didn't know what it meant. Personally I like boundlessdreamz's idea :)

Re: Bidding farewell to Google Code

#228

Earlier quoted context omitted.

It's not monoculture, there is also bitbucket which IMHO is much better product. Problem is that all the cool kids are now using github and if you want to look cool you also have to use github. Or you could just ignore the hype and use bitbucket.

I'm genuinely curious, what do you like better about bitbucket?

I really love the branch-level access control on Bitbucket. Being able to say that developers A,B,C have access to the repo, but only A can push to master, is incredibly useful.

Re: Bidding farewell to Google Code

#229
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,…

Last error report I created (which is consistently causing tab crashes) was marked as duplicate and merged (without comment) into an issue that is private and inaccessible. All attempts to get additional information have been met with silence.

That sounds like it means it's a security issue. All the browsers do this (the ones with open issue trackers, at least)

Re: Bidding farewell to Google Code

#230

Earlier quoted context omitted.

You said "absolutely no reason" and I gave you an edge case that invalidates your statement. Maybe "generally no reason" would be better?

Nothing in the world is absolute. However so far I have not hear any non nebulous reasons why an Open Source project should be on gitlab.

Because GitLab is open source, and the alternatives (GitHub, BitBucket) are not.
Post reply on HN