A lot of RSS fans (including me) are upset about this, as shown in this TechCrunch article. Although I use an excellent RSS aggregator, FeedDemon, at home, I use GMail and Google Reader via the Web at work, and I was somewhat put out that the link seemed to have disappeared.

As the TechCrunch article says,

You can customize Gmail to a degree, and – particularly for a free product – that’s really awesome, but you can’t yet change the order of the top menu items – and that’s what’s getting users riled up.

Maybe Google will listen to this vocal subset of users, maybe they won’t. But I think it may be better if we don’t wait to see what happens, and instead a TechCrunch-reading developer immediately starts coding a browser extension that puts the damn ‘Reader’ link back.

Since we can't install stuff on our work machines an extension wouldn't be any use to me, though ...

Another local blogger, The Greenwich Phantom, has picked up on the story and asks if this is the thin end of the wedge and if admission charges are to be introduced for national collections in general. While I can see some logic in these straitened times for introducing admission fees I do think that they way they have been brought in by stealth on this occasion has been handled particularly badly.

I agree with pretty much all of what is said, but with a couple of additions. They apply to cases when required fields are not completed and similar error messages are needed.

A lot of sites nowadays will, after you've pressed the submit button, process the form, sometimes taking several seconds, realise that a required field is missing, and finally reload the page with the error message at the top. Often, with fairly long forms, the page has scrolled down from the top so no message is visible and it can easily be missed. A variant of this is that the page isn't even reloaded; some CSS/JavaScript magic means that the error message appears without reloading. This is even worse, as I've several times thought that the submit button failed to work and continued futilely pressing the button. I've even gone back a page amd tried to start again.

There are some simple, easily-available, JavaScript solutions about that can pop up the error message in a box instead. Why on Earth can't they be used? The user can hardly miss the message when presented in such a way.

I suppose the site designers think that their methods are "cooler". <sigh>

In central London I saw a large truck manoeuvring slowly to make a left turn into a narrow street, made narrower by cars parked on each side. A car was waiting at a nearby junction with another street for it to complete the turn. As I walked along, a bus pulled up behind the car and the driver immediately started sounding his horn, obviously not seeing the truck. Losing patience after about a minute of non-activity, the driver pulled out his bus and overtook the car, coming face-to-face with the truck. Two other cars that were behind the bus and had followed hard on his heels were right behind him, so the bus driver couldn't back up again.

In the meantime, the driver of the original, patiently-waiting, car was able to squeeze past the truck and bus and go on his way, followed by a number of other vehicles. Since I turned out of the street at that point I didn't see how the remaining participants resolved the situation.

I might expect that sort of behaviour from some drivers, especially those driving white vans, but I have usually been impressed by the road sense shown by bus drivers. Not this time, though.