I'm not surprised, and yeah, I've assumed code on Google Code is abandoned by default. But, you know, just yet another Google product biting the dust.
While I've been sad to see a lot of Google projects come to and end I think this one is justifiable. I don't know of any active projects still hosted there.
Bidding farewell to Google Code
81–90 of 428 posts
Re: Bidding farewell to Google Code
#82Re: Bidding farewell to Google Code
#83Earlier quoted context omitted.
Honestly, I think he was right. Google has a really bad image problem right now where lots of people don't want to get involved with their projects because Google will most likely kill the project just like Reader and Glass. See my couple of wasted Google Glass devices that will never see an Android update again. Do you think I'll ever buy a Google Android product after they wasted $3k of mine? Do you think I'll buy…
> Honestly, I think he was right. Google has a really bad image problem right now where lots of people don't want to get involved with their projects because Google will most likely kill the project just like Reader and Glass. Again, these are two very niche projects. Reader was a niche within a niche. Glass was an experiment that a tiny subset of the population ever even touched first-hand. It never even reached a "…
Re: Bidding farewell to Google Code
#84Hi Chris, GitLab CEO here. What do you think about mentioning Gitlab.com as an alternative for people to move to? It has unlimited (private) projects and unlimited collaborators. It is based the open source GitLab project.
I second this motion. GitLab is amazing. It's open source and easy to deploy on your own hardware so you don't need to trust another provider. Github is really great for the social experience, but I've been debating switching over to GitLab for all of my development projects.
Re: Bidding farewell to Google Code
#85Earlier quoted context omitted.
Honestly, I think he was right. Google has a really bad image problem right now where lots of people don't want to get involved with their projects because Google will most likely kill the project just like Reader and Glass. See my couple of wasted Google Glass devices that will never see an Android update again. Do you think I'll ever buy a Google Android product after they wasted $3k of mine? Do you think I'll buy…
Killing reader was a terrible idea. That cut my daily google usage in half and was obviously a key social and relevance asset. Glass is still very much alive.
It sucks for our niche, but ultimately Google Reader was a product that didn't have any appeal beyond said tiny niche. The original goal was to make RSS more accessible beyond technologists, but it failed to reach any kind of mass appeal. Some of this was more to do with RSS/Atom feeds having some ergonomic issues that weren't solved before the social media frenzy took hold.
Failure is when results don't meet expectations, which is what happened to Reader. I don't fault them for closing it, despite it being inconvenient for me to switch. What does a for-profit company have to gain by dumping time and resources into a failure whose window of opportunity has passed? Some goodwill from a tiny, miniscule subset of their userbase?
Re: Bidding farewell to Google Code
#86Earlier quoted context omitted.
Honestly, I think he was right. Google has a really bad image problem right now where lots of people don't want to get involved with their projects because Google will most likely kill the project just like Reader and Glass. See my couple of wasted Google Glass devices that will never see an Android update again. Do you think I'll ever buy a Google Android product after they wasted $3k of mine? Do you think I'll buy…
> Honestly, I think he was right. Google has a really bad image problem right now where lots of people don't want to get involved with their projects because Google will most likely kill the project just like Reader and Glass. Again, these are two very niche projects. Reader was a niche within a niche. Glass was an experiment that a tiny subset of the population ever even touched first-hand. It never even reached a "…
Glass is clearly very much alive.
Re: Bidding farewell to Google Code
#87Earlier quoted context omitted.
Most of Google's open source code is already on GitHub and has been for quite a while: https://github.com/google
If you ever read any of my comments and down votes from Hacker News it was always this. The code on GitHub is a mirror and not an actual GIT repo that is accepting merges and being worked on.
Re: Bidding farewell to Google Code
#88Re: Bidding farewell to Google Code
#89Earlier 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?
Someone needs to do an Internet Archive style project on all these repositories, put them up on Github, and make sure that they are indexed properly by search engines (i.e. intro pages become README.md, wikis are migrated, etc.).
Re: Bidding farewell to Google Code
#90Earlier 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?
Someone needs to do an Internet Archive style project on all these repositories, put them up on Github, and make sure that they are indexed properly by search engines (i.e. intro pages become README.md, wikis are migrated, etc.).