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:
comments powered by Disqus

Related Posts

== and === in JavaScript and HTML Input Elements

If you read any current information about best practices in JavaScript, you will typically find the following advice somewhere in the list of things to do. Always use === and !== while avoiding == and != While I will never argue against this advice, there are a few things that a developer shoule realize when using === and !== instead of == and !=. === and !== first do a check of the data type of the two objects you are comparing.

Read More

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.

Read More

Estimating Software Development Projects is Hard

As a software developer, working with non-technical management and end users to define a deadline for when a project will be ready to use or how long it will take from start to end of a project is an extremely complex task. Unfortunately, the non-technical audience thinks that it should be simple to give some sort of estimation on the fly without detailed analysis of the project and what it involves, as it seems simple for them to estimate tasks that are like ones they have done before.

Read More