Just have the darned black box broadcast all of its data once every millisecond. Put receivers on satellites and on grounds stations or even on other planes. Give the transmitter a range of several thousand miles, and come up with some scheme to avoid broadcast collisions (either time or code division multiplexing).

If a plane goes down go back to the recorded transmissions, of which there should be multiple copies.

Converse All Stars. Don't know about high arches, but I too had foot pain at first after running in them. It subsided after awhile after the muscles, tendons and ligaments bulked up.

The reason you are experiencing pain is that one side of the thick wedges of foam in your shoe has lost it's spring, turning your shoe into a crappy little ramp that actually accentuates whatever that wedge was meant to correct.

The proper corrective for poor form is not a running shoe. It's either running barefoot, or running in a shoe with a thin rubber sole that serves as protection only. Try if for a month, but build your miles slowly. All the muscles, tendons and ligaments that your current shoes have allowed to atrophy will build up, and eventually you will be running like nature intended, with nearly perfect form.

You can protect your feet without slapping an inch thick slab of foam rubber under them.

I run in thin soled canvas shoes and have never had an injury from stepping on something. In fact I've had fewer ankle turn injuries as I can actually feel the surface and react if I've stepped on something that might cause my foot to slip or roll.

I code Android apps in my spare time. So basically I've got zero cost. Each of my apps has at least 3 competitors, which seem to be coded by people like me. Granted, many of my competitor's apps look like crap, but they work and provide a valuable service. Most people aren't going to pay top dollar for teh shiny - they are going to buy the cheapest thing that works. So I don't envision ever being able to charge a lot for my apps. I also don't see professional development shops being able to compete with zero cost hobbyists.

The apps are free because the Android market is in beta, and the payment system has not yet been activated. If I wanted to charge for the two apps I have in the Market right now I couldn't.

I don't know about whatever iPhone counterparts might exist for my apps, but they do what they do very well.

My apps run fine in the emulator at 320x480, no crashes.

Here is the deal, at 320x240, I go from 480 vertical pixels to 240. Ouch. Now I guess you could force the people who bought this new POS android phone to flip their phone sideways so that my app has 320 pixels - still quite a crunch - and have fun typing on this phone sideways.

But regardless, supporting such low resolution will take some doing on my part, and require me to maintain separate layouts, and possibly different code paths that reduce functionality or make other compromises. And at some point there are just some things that can't reasonably be done in half the screen real estate. I am likely not going to take the time to support such low screen resolutions in my apps.

I've developed two successful apps. One somewhat successful, one very successful. The most successful one is the most resolution independent. In coding it, I've done nothing that depends on any particular resolution. It randomly crashes in the emulator using QVGA (the resolution of the Aussie google phone). Even if it didn't crash, several of the screens are next to useless in the lower resolution, there is simply not enough space without recoding them.

Now, I could recode my app to use smaller fonts, lower the width/height of the UI components - but it would make my app less useful on the G1. Why would I want to do such a thing?

That's all well and good until I have to fit a certain amount of data on the screen. If I've designed for a larger screen, it's simply not going to fit, however flexible the layout.

Now I could design for the lowest possible screen resolution, but that will limit functionality or force me to produce a UI that's artificially small on larger screens.

Even the studious developers will have a lot of work to do making their apps work properly at lower resolutions.