I must speak out on the this one

Recently, while at work, I was discussing why Google maps do not include a scale. In fairness to Google, the maps may have this functionality, but I am ignorant as to how to enable this feature.

My hypothesis as to why there is no scale was a simple one. To accurately determine scale for a map, one would need to consider the topography of land the map covers. Maybe Google just does not want to go to the trouble.

Seems simple enough to me, but to my surprise, the other two parties in the conversation said that topography has nothing to do with scale on this map. Huh?!? I stipulated the point to avoid a nasty argument where more than one person might need to get schooled, Sesame Street style.

Well, I can't take it anymore; time for some schooling. The assertion I am attempting to buttress is that topography (whether there are mountains and valleys on the surface of the earth) matters when applying a scale marker on a map. Google could probably estimate this very accurately since topography overlays are available to them, but who wants to do calculus for such a small thing? Anyway, here is an image which details my explanation.

Installing Rails 3 on Debian Unstable (Sid)

Recently, I was installing Rails3 on my Debian unstable machine and I noticed an error that was really strange.

Here was the error:

ERROR NameError: uninitialized constant ActiveResource::Base

The problem ended up being that I was missing this deb file:

libopenssl-ruby1.8

I have seen posts from people proclaiming that uninstalling old versions of activeresource would do the trick, but I reinstalled activeresource-2.3.5 gem after Rails 3 starting working again without a failure. I hate cryptic errors like that.