Google Code Shutting Down

Google just recently announced that they are going to begin the process of shutting down their Google Code project hosting service. In the blog post announcing that they were shuttering the service, they let it slip that even Google had quit using Google Code for their project hosting, instead transitioning thousands of their projects to GitHub. Google seemingly blames the fact that GitHub and BitBucket handle project hosting better than Google does as the main reason that they are discontinuing the service.

However, what is really going on here is that Google is ending another one of its services that it has yet to find a way to monetize. With GitHub being so ubiquitous in the open source and enterprise markets, Google failed to make enough inroads into the enterprise markets to generate enough revenue to continue the service. Google’s other profitable product lines all rely upon harvesting the data you store in their services and to generate relevant advertising based on that data. This advertising model gets quite a bit murkier when the data is source code, something that, unless Stack Exchange is looking to advertise, has quite the narrow applicability to advertising revenue.

It seems again to tell us one very important thing about Google. If you choose to use one of their products, don’t be surprised when they shut that nifty product without much advertising down. The product that you know will keep going are those that are conducive to advertising, such as GMail, Drive, and Search, anything else may be fair game for a shutdown at any point in time.

Tags:

Related Posts

Mar 5, 2015
2 minutes

Don't Be a Dunce, Save Your Orders

There are some gotchas that you think that you will always see coming. One such gotcha is the need to save an object to the datastore to persist any changes you may have made to that object.

While it seems like a reasonable concept at the base level, there are times that the need to save an object completely escapes your mind. It seems that for many non-developers, this occurs when they have been working a long time on a file, typically a Microsoft Word document, shortly before their computer blue screens, losing all of their work.

#magento #web-development #php
Read More
Mar 13, 2015
3 minutes

Never Explicitly Trust Software Because It Is Open-Source

One of the major ideas behind open source projects is that allowing anyone that wants to view the source code of a project to be able to do so should make bugs and security weaknesses easy to find. While this did not work so well with OpenSSL and its various bugs that have been exposed recently, I do have an example where it worked extremely well.

Magento is an eCommerce platform that has two separate editions. One is a completely open-source and free as in beer Community edition. The other is a somewhat expensive Enterprise Edition. There is a large community of Magento developers that create extentions, or addons, for these two editions of Magento.

#magento #javascript #web-development
Read More
Jul 8, 2014
3 minutes

Always Use Automated Integration Testing

QA or Quality Assurance of a software project is often the area of software development that is most neglected. Typically developers avoid software testing like their lives depended on it. While a basic level of testing is required for a single scenario to validate that your code “works”, the level of testing that is required to ensure that all users have a good user experience across all targeted platforms is something that a developer seems to think is beneath them.

#javascript #microsoft #design-patterns
Read More