Skip to main content

iGoogle versus Netvibes (versus Yahoo! versus MSN versus A Billion Others...)

The gloves are on, the bookies are taking bets, and everyone is gathering around for... wait, wait... does anyone care? I don't. Here's why.

Seriously who uses these things? Do you have such a light inflow of email and feeds that you can afford the time to keep these Yahoo-loving pages up to see and barely do a damn thing? If you aren't keeping this page as your top window, there is little point. The whole thing is about passive information. Oh, look at that quote. Hmm, its 7 AM.

If we're going to build web services that collect a lot of tools around a single page, then personalized home pages are entirely the wrong direction to take. We're an always on kind of computer using society, so how often do you see a homepage? Hell, I don't even set my homepage anymore, because I only see it once every month or so.

However, I do have my feed reader open and look at it at least once per hour that I'm actually at my computer. I can't think of anything that couldn't or shouldn't be pushed right through there. My GMail inbox, event notifications, quote of the days, and everything else would be far better pushed through one hole: my reader. The fun little widgets are interesting distractions, but they don't have a place in a reader, and there really is no love loss there. They serve no purpose and even as entertainment are barely on anyone's radar.

Again, however, there are some cases where the things we're doing in widgets could easily be adapted to a feed environment. Take, for example, the common widget/gadget in all widget/gadget families, which might be a simple 15 Pieces game. It would make no sense to have such a widget (and many widgets are equally insensible), which takes up space to be so sparsely used. Sparse used doesn't diminish the actual use, so how can it fit? Let it come up in my feed reader every now and then. I can play a bit and then continue reading, knowing that it will come around again to continue later. Information is nice when its in tiny chunks.

Comments

Popular posts from this blog

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...

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...

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...