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

241–250 of 428 posts

Re: Bidding farewell to Google Code

#241

Post by fixermark »

aikah wrote: post #180

I knew it ... what a shame. You know what killed that product? BAD basic UI/UX. it was horrible to use an naviguate in,so people moved to something with better UX, better design and better visual. Google puts 0 efforts in these things, at least in the browser. Funny how then Google comes with "material design" , but can't update a few CSS on its old apps... Github didn't get popular because it was written in Ruby(tho…

If by "Google app engine console" you're referring to https://appengine.google.com/, that's already in fact "dropped." Check https://console.developers.google.com.

The App Engine UI is getting an overhaul; App Engine as a product is probably going to stick around.

Re: Bidding farewell to Google Code

#242

Post by cdibona »

wldcordeiro wrote: post #69
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…

I had my hopes up that you guys would update Google Code to be more of a contender with GAE and Compute integration.

I have a secret desire to reuse the code domain in this manner.

Re: Bidding farewell to Google Code

#243

Post by sytse »

the_mitsuhiko wrote: post #186
ericfontaine wrote: post #173

Earlier quoted context omitted.

"There are many other hosting services like gitlab, what would make gitlab different so that it would deserve a pitch there?" Which is why I said the blogpost would be fairer to just post the wikipedia comparison link. I never said that gitlab should "deserve" a pitch on the blog. I did say it was fair for GitLab to pitch their services, as the CEO has done here, but that is different from "deserving" a pitch. It is…

> It is hard to objectively determine what is the better hosting, but based on people's individual preferences, they can subjectively decide for themselves, which the wikipedia article helps out by clearly explaining the differences. It's quite easy to tell actually. Responsiveness of the UI, featureset, availability, size of the community. * Gitlab is measurably slower (it takes about 5 seconds to load the commit pa…

Thanks for the concrete examples.

GitLab is faster in on some pages. The commit page probably is slower, but not by so much:

wget https://gitlab.com/gitlab-org/gitlab-ce/commits/master master.1 [ ] 66.40K 382KB/s in 0.2s

wget https://github.com/gitlabhq/gitlabhq/commits/master master.2 100%[=====================>] 183.50K 662KB/s in 0.3s

Again, your milage may vary (cache) and I do agree that the commits page of GitHub feels faster most of the time.

GitLab doesn't have preview support for as many features as GitHub, but it has many other features GitHub doesn't have such as protected branches and git-annex support (version large binaries with git).

There are less integrations than GitHub but I would not say there is a lack of them https://gitlab.com/gitlab-org/gitlab-ce/tree/master/app/mode...

We think the issue tracker is good, working with labels can be improved but getting a milestone overview across projects is pretty sweet.

Availability of GitLab.com is over 99.9% at the moment http://status.gitlab.com/

Over 700 people have contributed to GitLab http://contributors.gitlab.com/

We understand if people place open source projects on GitHub, they have way more registered users. But some people choose GitLab and their numbers are growing.

Re: Bidding farewell to Google Code

#244

Post by grizzles »

cdibona wrote: post #150
shubhamjain wrote: post #38

Earlier quoted context omitted.

While true that no one uses Google Code. Every now and then, I bump into some obscure but a little useful project being hosted on Google Code. Maybe, makers of those projects have grown out of them and don't wish to put any more effort but still, there is a bit of value, I am able to derive from them. What will happen, if those projects are not migrated because their developers have simply forgotten about them?

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

Thanks for this, Chris.

Could you publish a list of projects w/descriptions? That would be great for others (gitlab?) who might want to host / cherry-pick / curate the collection a bit more than that.

Re: Bidding farewell to Google Code

#245

Post by matt_brushlabs »

sytse wrote: post #212
FlyingSnake wrote: post #200

Earlier quoted context omitted.

We use GitLab internally, and it's an amazing piece of software. It's open source, easy to setup and is pretty robust. I would love to see the option to move from Google code to GitLab.

We do too, it would be nice if someone can contribute an importer.

I certainly hope GitLab uses GitLab internally. ;)

Re: Bidding farewell to Google Code

#246

Post by robbrit »

zorpner wrote: post #157
jdmichal wrote: post #45

Earlier quoted context omitted.

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?

At least from my perspective, the problem is that Google sometimes releases into already-existing fields at a price point no one can compete with, absorbs the entire market, then pivots away. This is pretty destructive behavior, and I think fundamentally different from entering a field in which you intend to try to run a business (as opposed to subsidizing your entry into the field with profits from elsewhere in the…

Except in this case they didn't absorb the market and then pivot away. The market moved away from them and consequently they shut down a service that nobody really uses anymore.

Re: Bidding farewell to Google Code

#248

Post by myohan »

GitHub wins! I think it's good that Google indirectly admitted their service is not as good as Github, now they need to do the same thing about Google+. Google, you are an amazing company but sorry you can't possibly be the best at everything.

Re: Bidding farewell to Google Code

#249

Post by serve_yay »

rdtsc wrote: post #135

Anyone else scared of the Github monoculture? I am. For all the touted distributed version control advantages we now have one world global centralized repo. Yeah, yeah, I know you can clone it locally. But of course if all the issues, and testing, and build tools are tied to Github. Isn't it a bit disconcerting? Maybe I am just paranoid. And not saying that Google code was going anywhere, I saw more and more projects…

In addition to Github, we also use Atlasssian Stash. And let me tell you: I am not afraid of the Github monoculture.

Re: Bidding farewell to Google Code

#250

Post by zorpner »

robbrit wrote: post #246
zorpner wrote: post #157

Earlier quoted context omitted.

At least from my perspective, the problem is that Google sometimes releases into already-existing fields at a price point no one can compete with, absorbs the entire market, then pivots away. This is pretty destructive behavior, and I think fundamentally different from entering a field in which you intend to try to run a business (as opposed to subsidizing your entry into the field with profits from elsewhere in the…

Except in this case they didn't absorb the market and then pivot away. The market moved away from them and consequently they shut down a service that nobody really uses anymore.

Sorry, should have made it more clear that I wasn't talking about Google Code specifically, but was responding to the parent comment regarding "release and pivot".
Post reply on HN