Skip to main content

Google Loosing the Charm?

For years we've been so in love with Google. Don't deny it, a part of you smirks or even cringes when you see a colleuge searching with Yahoo or MSN. You feel better than "those hotmail kids" because you are @gmail.com. Google is at the forefront of all that is technologically good and righteous, and we just can't get enough.

I think I've had enough.

Why am I using Microsoft's Live Earth instead of Google Maps/Local (they can't seem to draw a good line between the conjoined services)? Live's Image search is enough to make Google Image look like a cheap gallery on a geocities page. YouTube consistantly provides better content than Google Video, whose saving grace is the large video size by default and that you can rent Night of the Living Dead. I'm desperately looking for something to replace Google Reader for my feed consumption, and eagerly awaiting Divmod to reopen Quotent so I can pay them to not have to use GMail anymore. Google recently launched their long-rumored calender service, and I've been using it but am continually frustrated by the interface's inconsistancies.

The various things that lead me to realize more and more that Google isn't so fantastic have also opened my eyes to an interesting revelation: their web-app interfaces are pretty poor. Simple is good, so they seem to drop features just to make it look clean, but end up with a stump of what could have been. And, I'm continually tired of the lack of interconnectiveness with all the Google app's that I use. Blogger, GMail, Reader, Calender, and its like I'm using them all from seperate venders.

Google, what are you paying all those PhD's to spend the 80% of their time on? At the rate Live is improving and companies like 37signals are tossing out great web-apps, you're going to fade away and be lucky if you salvage a place in the world as a mediocre advertisement channel.

Comments

Popular posts from this blog

My Software Job Transition Strategies?

I’ve been spending a good deal of the last two days preparing mentally for starting a whole new challenge as a developer. New things aren’t new to me, but this is different and big enough really call for some Deep Thoughts ™. For one thing, I’ve made a big move from the world of Python web development to totally other Python work and while web development has never been the only thing I do, it has been the only work that paid the bills. That transition isn’t one that bothers me or daunts me, though. Instead, I’m thinking about transitioning to the scope of the work I’m getting into. For a long time, I juggled multiple clients and client projects every day, so no single project usually took up most of my time. Every developer juggles time through the day, but exactly how that works in each company and on each project varies a lot. I was looking for a place that I could really focus in a way that I haven’t for a long time. I think I found that, but now I have to deal with the consequen...

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...

The Snake Pit is About to Burst

The signs are all over the place. I can count at least five implementations of Python today: CPython, CL-Python, Jython, IronPython, and PyPy. The use of the language is sky rocketting and set to grab real mind-share as the hype over Ruby subsides. Things are looking good for a favorite green snake and british comedy troop reference, aren't they? Trouble is on the horizon in the very ingredients that could push us into true success. Our community and our very language is in danger of segregation, unless we all do something about it and learn to get along. One of the most visible dangers (to me) is being ignored for various political, cultural, and non-technical reasons. IronPython's users are increasingly pushing IronPython-only recipes, libraries, and tutorials. No one is talking about the transition of the alternative implemenations to CPython 3.0 compatability. To make matters worse, we still can not define the language without refering to an implementation. This is very un...