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
Jul 11, 2014
3 minutes

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.

#responsive-web-design #rant #web-development
Read More
Jan 8, 2015
3 minutes

Write Bulletproof JavaScript

While display issues have long been the bane of a web developer’s existence, current web development projects tend to have much more client side interactivity, focusing ever more attention on the reliability and resilience of the JavaScript you write to deliver the complete interactive experience. Many things can cause unexpected errors in your carefully crafted code.

However, there are a few things that you can do to make sure that your site degrades gracefully and still provides a basic level of functionality when something in the browser goes wrong. The following snippet of code illustrates a few best-practices for defining your JavaScript namespaced modules.

#jquery #javascript #web-development
Read More