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

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro...