571 karma · joined September 9, 2012
Again, could you explain why you chose that headline? Perhaps because it would grab attention?
For me, all it did was turn me off your book.
What's next, some other people writing a book about Scott Forstall or Bertrand Serlet, saying "Jony Ive never coded. Did we give credit to the wrong guy?"
Why not just focus on the people you want to cover, without asking the unnecessary question "Did Steve Jobs get too much credit?"
The development costs are higher, but with some investment it's certainly possible for a small startup to create new CPUs and GPUs. Gaining market share is more difficult which often necessitates a huge established chip company as a backer.
Arduino gets you quickly up and running, without spending days fiddling with compilers and settings just to get something working.
And so is this: http://dx.com/p/arduino-compatible-gsm-gprs-shield-wireless-...
And this (includes an Arduino Uno compatible board for $80):http://dx.com/p/elecfreaks-diy-gprs-gsm-learning-development...
There are several unlocked GSM shields and modules available with working libraries and tutorials for under $50, using the exact same GSM module (SIM900): http://dx.com/s/Sim900?category=499
If you want links to examples of PED interference, I've posted them elsewhere on this thread. All anecdotal of course, but there are enough examples that to say there's no chance if interference would imply a secret conspiracy amongst pilots to file false reports.
And again, you are misunderstanding the concern. It's not whether a cell phone can stop the airplane from working and make it fall out if the sky. It's whether, at a critical time such as during landing and takeoff, it may cause interference that can increase the pilots workload and contribute to an accident.
Search for "laptop" and you have a few examples of spurious TCAS RAs.
In some older report there was a specific instance where the pilot out of curiosity had the passenger turn the device back on, and had the problem reappear (this was in cruise so there was more time to debug the problem). Google for NASA PED reports and it should be in one of them.
It's really, really, really small, with millions of successful flights done without problems. Yet accidents like those have happened, and have been prevented after that rule was put in place.
I was using mathematical proofs as an example of why in IT security, often times since you can't be sure, you do the proactive thing and don't run services exposed to the internet. If you have a database with credit card numbers, you don't let the DB listen for connections on a public IP, not because you think there is a security hole in the DB, but because you can't be sure there isn't.
I suggested getting a PPL to get rid of all those annoyances that commercial air transport impose on you to reduce their risk. There is even an experimental airplane category if you want to err on the risky side.
I agree that it has to be approached analytically, but since you can't prove a negative, in the end you have to make a risk assessment. I certainly don't agree with all of them, but there have been enough examples of fatal accidents when the FAA didn't do their job, that I'm happy that they are taking their time to, guess what, do the analytical work, before changing a regulation. As opposed to acting on a gut feeling about what would be safe.