Quickly, convert from 1234 kiloinch to miles!
$ time units -v '1234 kiloinch' miles
1234 kiloinch = 19.47601 miles
1234 kiloinch = (1 / 0.051345219) miles
That didn't take to long at all!
Seriously, the metric system has a lot going for it in some ways, but is harder in others. For example, while 10 is a great multiplier (since we tend to think in base 10), it doesn't have a lot of factors. For example, dividing by 3 doesn't work so well. Sure, you and I know that 1/3 meter is 33.33333 cm, but that's not as easy as 1/3 foot being 4 inches. 5280 (the number of feet in a mile) is divisible by 2, 3, 4, 5, 6, 8, 10, 11, 12, 15 and a lot more. Not that a 15th of a mile comes up a lot, but if it does, you can be assured that it's exactly 352 feet!
The metric system units are also more calibrated to scientific use than everyday use. The meter is too long and the gram is too light (the liter is about right). Other things, like degrees Celsius are too big (not to mention as arbitrary as Fahrenheit). And metric time never really took off -- you still have seconds, minutes, hours, etc.
All in all, the metric system is optimized for scientific work where conversions between units happen more often, and knowing that 100 million micrograms is
Kano points out the verse from 1 Corinthians, but there's also 1 Timothy 1:10. The word translated "homosexual" is arsenokoites. This word is derived from arsen, meaning "man", and koite which is the root for the Latin "coitus". There's also Romans 1:26-27. Now clearly there's some disagreement on what these verses actually mean, but it seems clear to me, at least, that Paul agreed with the Mosaic view that homosexuality was abhorrent to God.
I almost agree. I'm sure there are niches where on-line document editing has merit, but the bottom line is that cloud computing is still more vapour than solid software. On-line office suites suck in almost every other way compared to their desktop-based brethren, and it's not as if there's no scope for improvement in those, they've just reached the point of being "good enough" that people tolerate their problems.
I can't help noticing that every time someone makes observations like these on forums like Slashdot, there are usually a string of responses about how trusting Google/Amazon/whoever with your sensitive data is better than trusting in-house people who are still a security risk, don't have the same resources to build in resilience to system failures, and so on. And then over the following week, it always seems like there are a couple of articles about major downtime from such services, another one about a serious security breach, and every few weeks there's a major data loss incident.
In any case, while centralised storage has merit for some purposes, you don't need software-as-a-service for that, you just need somewhere you can save a file.