Skip to main content

Trusting Google.

Consolidating resources to better serve users was the motto behind Google killing various services. But a seriously, Google reader? Reader is one of the first prominent services from Google. It belongs to an elite club that enjoys a loyal use base and plethora of third party apps. What's their fate. On a larger scheme, Is Google trustworthy anymore?

Last week Google released this announcement
We launched Google Reader in 2005 in an effort to make it easy for people to discover and keep tabs on their favorite websites. While the product has a loyal following, over the years usage has declined. So, on July 1, 2013, we will retire Google Reader. Users and developers interested in RSS alternatives can export their data, including their subscriptions, with Google Takeout over the course of the next four months.

First, I was so sure it is a run up to a cruel gag for this year's April 1 (still hoping it is). But now, Google reader is no longer in the "More" menu bar. The truth is slowly sinking in. The phase of denial quickly fading. Very quickly Google became an "unreliable" company. Google killed other "Lab" products before, citing lack of user base. It won't be so easy for Google to wasgh hands off Reader using that excuse. The decision appears to be another failure of Google to understand "Social" - If they had to do this anyway, they probably should have come up with some alternative within Google+ for RSS before announcing the kill.

In the recent past, Companies that put $$$ before innovation are growing by the day - Oracle, Microsoft, Apple, Google.. So if you are an open source developer or otherwise - investing time and resources in API's from them, How sure are you that they will be around?

Now, Google just announced (and released) Keep. Google's take on Evernote. Releasing Keep within a week of Reader's announcement only hurt its chances of launching well into a strong user base. The general dissent towards Google's policy is confusing at best and Alarming at worst. How long will Google keep the other services around. Will it pull the plug on Photos, even Gmail (Google recently removed free version of Google apps for hosting email). Irony is - this and many other blogs that are crying foul on Google's decision are hosted on Google's blogspot.

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...