Completely agree. I'm surprised that, especially on HN, the large number of people who won't apply Occam's Razer to the situation.
I imagine that most air accident investigations begin like this; confused, competing information from numerous sources of varying reliability. Just with the internet and 24h news, everyone is following along with each revelation (see also the Pistorius trial).
Give it some time, let the investigators work and report their findings. I'd be very surprised if it's not a combination of system failure and human error in reacting to the failure.
> I imagine that most air accident investigations begin like this; confused, competing information from numerous sources of varying reliability.
Not to mention that but when things happen on the plane, pilots are given confused, competing from numerous sources. This is why I assumed it was an accident (like Air France 447) at first.
> Give it some time, let the investigators work and report their findings. I'd be very surprised if it's not a combination of system failure and human error in reacting to the failure.
That was my first impulse too. Google "IEEE Automation Paradox Air France 447." However, this is really hard to square with the engine information. So you have three possibilities: the plane flew an uncommanded course on autopilot for 5 hours following an accident, the flight data is wrong, or it is a hijacking.
In this case an investigation is hard because there is so little information. It took until the black boxes were recovered from AF447 to determine what happened there. Here? We don't even know where the plane is, much less the relevant recorders.
Ross Anderson sums this up nicely in "Security Engineering":
"I write ‘identity theft’ in quotes as it’s a propaganda term for the old-fashioned offence of impersonation. In the old days, if someone went to a bank, pretended to be me, borrowed money from them and vanished, then that was the bank’s problem, not mine. In the USA and the UK, banks have recently taken to claiming that it’s my identity that’s been stolen rather than their money, and that this somehow makes me liable. So I also parenthesise ‘victims’ — the banks are the real victims, except insofar as they commit secondary fraud against the customer."
I meant for a native app and you being the provider. If you don't trust the client app even oAuth won't help you preventing the client app to know the user password.
Attribute access of namedtuples aren't any quicker as you've surmised, it requires a hash lookup and an index lookup. Index lookup is as quick as normal tuple index lookups. The main reasons I reach for namedtuples is memory efficiency and much quicker creation times vs objects.
Memory efficiency? The last time I checked namedtuple dynamically generates code for a class with the specified fields, and evals the code. So it would be exactly as efficient as a normal class. For memory efficiency you want to have multiple points in a single array, to avoid the overhead of objects, but you'd need Numpy or Cython for that.
Right. But you can fit 2 floats in 8 bytes so if it's memory saving and efficiency you're after, you would use an array to avoid object creation overhead. Namedtuples are nice for their self-documenting properties though, but it's misleading to advertise them as an optimization.
