cloud SLAs are a joke. That's the point. If a cloud outage takes your application down, the appropriate parties to blame are those responsible for application design and operations architecture. You can't just take an app designed for a datacenter and naively move it to amazon and expect HA. You need to design for failure and automate the hell out of provisioning. The ideal is to either load balance across multiple providers or automate the living hell out of provisioning and backup until you can reliably get DR times in the 5 minute range.

Yeah, I love opening a web browser to make a phone call from my chosen phone number.

oh, that and it works with the ipod touch if you buy the kit.

Thanks for your useful input. I'm glad that, knowing nothing about the question asked, you decided to answer anyway.

This app behaves much more like a standalone GPS device that you can mount on your dashboard; it has preloaded maps, 3d perspective, voice prompts, offline use, etc.

I've been using garmin's GMobileXT on my S60 phone for a while, which is pretty much an exact port of a low-end Garmin device, except it has data access and can use AGPS for faster locks. It's kind of nice for trips but 99% of the time I just need a quick answer, and the google maps application is more than acceptable (plus, it's been getting better and better lately: now it's got street view, latitude, layers, transit directions -- it already owns offline apps in all respects except voice prompts and the fact that you have to constantly press zero to recenter on your location.)

They're hardly standardized. Looking at the wikipedia article on cursive, I was taught different forms of several of the capital letters. I find that a lot of cursive is contextual, words just turn into spaced humps with ocassional curls and vertical lines. It's no wonder that it's so hard to read.

to add a datapoint, I'm 24 in the US and our school had mandatory cursive instruction from first through fifth grade. As in it was a class given euqal time as History and Math. In retrospect, that's just stupid. Except when i have to decipher notes from my grandmother.

I just generate output graphics as files and open them on my machine over sftp. A whole X session seems like monstrous overhead for a transaction that is 99% text and an occasional image file.

http://www.dasher.org.uk/dasher/download/linux/maemo/4.1/dasher_4.1.4.0inferencemaemo1_armel.deb

By far the best feature of the Homecinema fork is its ability to completely remove tearing when you enable Direct3D Fulscreen in the Output settings. Every computer I've ever owned exhibits some tearing when playing 720p/1080p content, and it's especially bad on integrated graphics. Without exception, mpc-hc eliminates this.

FYI, Nokia has a N810 successor planned with OMAP3 and HSPA, probably out by Q4.

http://arstechnica.com/tech-policy/news/2008/12/fcc-oks-analog-nightlight-rules.ars

The money is derived from the sale of the bandwidth, not your tax dollars.

Since interoperability is key in this context, anything besides FAT32 is hopelessly esoteric. So why not test the OSS solution as well?

Despite living in a WiMax city, I'm holding out for the N900; I just hope it's here sooner than Q3.

NPR is great. Since I figured out how to rip the mp3s off of their flash stream of Morning Edition and All Things Considered, I barely listen to any other podcasts. It's like having 60 Minutes on 14 times a week. And that's intended as a compliment.