Agreed. Why not just .s? Or maybe .sec?

My guess would be better coverage of the intended area with fewer satellites. A geo-stationary orbit would yield constant coverage with a single satellite. Whereas in LEO, the satellite orbits every 90 minutes so it would be out of contact every 45 minutes (probably more) while it's on the other side of the earth, requiring more (expensive) satellites to be launched.

As for ping times:
LEO: ~350km (approx height of ISS) = 350km/c = 1.16ms * 2 = 2.32ms
Geo-Stationary: ~35,000km = 35,000km/c = 0.116s * 2 = 0.232s = 232ms

References:
http://imagine.gsfc.nasa.gov/docs/ask_astro/answers/970408d.html
http://en.wikipedia.org/wiki/Low_Earth_orbit

After all, don't people realize the horrible things that can happen when someone gets offended?

I found this documentary about the terrible consequences of being offended. It recounts the gruesome details of people who have been offended, went to sleep, and woke up the next morning with leprosy.

It's good that Pakistan is stopping these atrocities before they get out of hand.

256MB (or less): My main computer is an iPad 1, iPhone 3GS, or low-end android phone

256+ to 512MB: My main computer is an iPad 2, iPhone 4/4S, or a mid-range android phone

512+ MB to 1GB: My main computer is a high-end android tablet

1GB+ to 2GB: My main computer is about 5 years old

2GB+ to 4GB: My main computer is about 3 years old

4GB+ to 8GB: My main computer is about 1-2 years old

8GB+ to 16GB: My main computer is a high-end workstation

More than 16GB: My main computer is a server

I thought you were talking about this great new Apple product

Reminds me of:

Yeah, it's close, but not perfect. However, the Mozilla extensions are more along the lines of what I was thinking.

That Mozilla link is along the lines of what I was thinking of for dynamic audio. Too bad it's not supported by all browsers, but it would be a start. With some proper architecture, it should be easy enough to add support for other browsers when they support a similar feature.

Thanks!

I should probably start looking at what it would take to port my Flash NES emulator to JavaScript. I wrote it in Haxe with the goal of doing a JS version at some point. However, at the time, only Chrome could even come close to running the JS fast enough, but now most modern browsers should be fast enough (I'll have to do some performance tests). It should just require minor tweaking to replace the flash calls with JS/HTML5 calls without having to re-do and re-work the bulk of the logic.

I'm curious how he plans on handling dynamically generated sound from the GB ROM. Doing CPU and Graphics are usually the easy parts of emulating, but getting smooth dynamic sound without much latency is the challenge I've had to deal with when doing web-based emulators. Most web-based systems are designed to load a static set of sounds from a server, not dynamically generate them in the code.

Flash 10 provides some dynamic sound capability, but it has a rather large latency (~250ms). I blogged about this while writing my NES emulator in flash.

I read through these articles hoping for some insight on dynamically generated sound, but it doesn't look like he's gotten that far.