Wi-Fi Coming on U.S. Domestic Flights
jvptoad writes "The NY Times is reporting that United Airlines has received approval to offer Wi-Fi Internet access on its planes. Although it will be over a year before the service is available, I wonder if this will impact the discussion on cell phone usage in planes (which seems to be centered around the annoyance of people talking loudly on the phone). Add a headset and Skype, and you don't need a cell phone to have loud, annoying phone conversations on an airplane."
Either that or get some good headphones, because if you start playing Duke Nukem on your laptop when I'm sitting next to you, I'll be showing you where the off switch is.
Sorry, your right to infringe on society ends where my eardrums attached to my body stuffed into a seat where your laptop requires you to lower your tray table for the whole flight begins.
And if you don't like it, fly first class.
-- Tigger warning: This post may contain tiggers! --
I have to admit that I would probably use this quite a bit to check my email and play on the web on flights.
However, I'll miss the fact that there was a space where I couldn't do those things. There's so much pressure on people to be available all the time, that it was nice to have forced downtime.
What is it with you people who get upset when people talk on a mobile phone? Do you also get annoyed at people talking face to face in your presence? Do all forms of conversation in which you are not involved annoy you, or is it just the ones using a form of technology?
For the longest time airlines were telling us not to use electronic gadgets, fearing "interference with the navigation system." Well, if they're OK with having bunch of passengers putting out 1 Watt each @ 2.4 GHz, how come they were objecting to the little blackberry (albeit at a different frequency) and other two way radio devices?
No, you cannot listen to your ipod 10 minutes either side of take off and landing because you need to be able to hear any emergency announcements coming over the intercom. Not because your ipod interferes with cockpit controls.
Never was an interference problem in the first place.
Oh well, what the hell...
I think the difference being that the FAA is allowing them for US flights.
Actually, people seem to yell (or talk very loudly) into cell phones because...
:)
"I SAID that the reception sucks! Yes, SUCKS. Are you listening to me? No. Yes, no. TURN OF THAT NOISE DAMMIT - oh wait a second. Waitress, mind giving me an extra soda? Thanks.
No.
Yes.
No.
I _DO NOT_ appreciate yelling!
(at some point, someone tells me to lower my voice tone)
I can't help it, reception is awful, and look, if they allowed phones, it was for a reason.
Moron...
No, it wasn't to you.
No, i said it wasn't to you! There's this idiot next to me telling me to shut up.
Yes.
No.
FINALLY!! Well I have to go to the bathroom, I think that lobster is giving me nausea.
I said NAUSEA! Good bye!
*CHIRP*"
I hope that clarifies why it's annoying
1. you need to do physical installation into each seat
2. you need to run wires from each jack to some central location
3. the jacks and wire add up to a fair amount of extra mass, which means the plane needs more fuel and can carry less payload
4. not everyone carries an rj-45 patch cable, so the airline will need to keep some handy (yet more mass)
5. little kids will stuff action figures or food into the sockets, destroying them or even shorting the whole network out
Really? You mean you don't have anything equally important that you could work on that doesn't require real-time connectivity? I find that very hard to believe. Perhaps you're just one of those people that constantly checks email and IM instead of doing real work (the stuff you could do offline). How many technology jobs *require* constant real-time connections? I'm sure they exist, but I can't think of many.
Latency only matters for time-sensitive applications like games. You're crazy if you want to try playing games on airplanes. Your e-mail already takes minutes to go between servers, and web pages often go years between being posted and reaching you. Latency will be at most a few seconds.
If the airlines don't want people using skype or VOIP in general, they can set up a firewall/proxy so it would not be possible.
:-)
yes, there are l33t hackers that would create a VPN tunnel via HTTP or some other such shit, but the majority of general public don't have any idea how to do that.
also, it could be a matter of policy - if they catch you being loud when you're not supposed to, they can tell you to stop, and if you don't - someone in a uniform will be waiting for you when you get off the plane
--- sig moved for great justice.
(I am a private pilot). If you are flying in IMC (Instrument Meteorological Conditions - on instruments alone), you have placed the lives of your pax in the hands of the pilot and his instruments. There are no outside clues when things go wrong. See here
for the top 100 air disasters. Two of them were purely ILS failures.
I'm not so confident that it can't happen. There are numerous anecdotal stories in the industry of NAV equipment wandering off course. In 1999 there were 76 reported incidents of possible cellphone interference. On IMC, and especially when on approach, these have the potential to end in disaster.
Still... real-time data connectivity while in the air will greatly increase my productivity while flying.
That, to me, is a drawback. I don't WANT to be productive on a flight. It's nice to have a place where you're guaranteed to not be able to work.
Does it surprise you that the US gets it after everyone else? That's pretty common in the technology world.
Access to version control/searchable hyperlinked documentation/build servers isn't important? How many corporate development architectures fit onto a laptop?
He said it made him more productive. It does. Rooting around on my hard drive for ADC docs is much more time consuming than typing into google or a search box. What about that library you didn't think you needed the docs for because you weren't using it directly?
Now that I'm used to having the internet and google as a resource at work when writing code, it's harder to do it the old fashioned way. There's no reason to anymore. Once you've built a development methodology, messing with it by removing internet access is a *bad idea* and likely to introduce bugs and inconsistencies.