The switches require that you pull them out, move them to the end position and then push them back down, and it was two switches. It could have still took off on one engine. This is essentially the turn off plane switch. It would seem to almost impossible that it would be an accident.

Not possible it's an "I bumped it" type of accident, maybe.

It's quite possible it's a "performed the wrong muscle memory at the worst possible moment" type of accident. This is unlikely, but anyone who thinks such a mistake is impossible doesn't know anything about human factors.

Unlikely just means "low probability." There are thousands of flights per day, so it's only a matter of time.

There is a difference between will have, and does have.

He didn't speak to why he's using NSLog. There are better alternatives that player nicer with Swift. https://developer.apple.com/documentation/os/logging

> A few years ago Apple introduced a new logging framework called the Unified Logging System, which supports logging with variadic arguments from both Swift and Objective-C. It also supports a host of other features that allow you to categorize and prioritize your log message and, well, it sounds great, but it’s also quite a bit more complicated than just invoking NSLog. It’s complicated enough that I can’t offer a one-line fix for the situation I’ve described here, but I encourage you to investigate your options.

Unified logs are an overkill API that isn't particularly well-suited for general purpose use like NSLog is. It's really more of something Apple uses themselves that they decided to throw over the wall for third party developers to adopt, but very few have done so due to its strange interface and goals that don't match what most app developers want.

The article implies that the code was ported from objective-c to swift.

No, the 10k wasn't charged until the last year when all new cars had the hardware upgrade, but nobody should pay for FSD until it's out of beta.

$10K is the current price. Early last year it was $7K. The price used to be around $2K. Regardless of the price, Tesla is selling a product that it may never deliver.

Unless AP doesn't allow the driver to control the vehicle it is the drivers fault.

You're not alone.

Let me guess, 6 months of free credit monitoring to make up for it.

Future Not-The-Onion: "Most Americans have more free credit monitoring than their life expectancy".

New startup idea: Credit monitoring monitoring

Our children will fight for single-payer credit monitoring.

Just talked to God, this is what he said.

Your fingerprint data is encrypted, stored on device, and protected with a key available only to the Secure Enclave. Your fingerprint data is used only by the Secure Enclave to verify that your fingerprint matches the enrolled fingerprint data. It can’t be accessed by the OS on your device or by any applications running on it. It's never stored on Apple servers, it's never backed up to iCloud or anywhere else, and it can't be used to match against other fingerprint databases.

https://support.apple.com/en-us/ht204587

I just took a random survey of 5 people around me. 5 out of 5 didn't know that, and assumed Apple had a copy of their fingerprint.

The point, in case you missed it? The fact that privacy is not actually given up doesn't matter. People are willing to give it up to gain some perceived benefit.

Exactly. I'm a fan of Swift on the server, but this is the best they can do with marketing?

It's still early, 2017 will be exciting times with Swift 4.

That's where we are coming to share more of SSS topics in https://www.facebook.com/ServerSideSwiftCommunity/

Yes, as part of a project that has used Swift for the last year, migrating away from Objective-C on a decent size codebase, I can say it is not ready for primetime.

Swift 2.2 + Xcode 7 wasn't great, but it was livable.

Constraint SourceKit crashes makes Xcode essentially a text editor and not a good one. All indexing, highlighting essentially all IDE functionally lost.

This is the worst development experience that I've seen in 20+ years as a developer.

I thought the CoreData / CloudKit debacle from 3 years ago was bad, but oh my God, I just want to jump ship and go to Android, switch to Xamarin, or just leave mobile at this point.

It would be nice to have some level of optimism and say this is growing pains, but I don't have any faith that the Apple developers are competent in making this better.

Most of my problems seem to be with Xcode. The crashes can be pretty frustrating, and most I encounter are repeatable (which makes me think they should of been caught in testing).

The failure in releasing Xcode 8.2/iOS 10.2, but not updating the iTunes Connect backend to allow iOS 10.2 as the max was pretty disheartening. All apps were automatically rejected for half the day. How does something like that slip through the cracks? To find out if it was fixed I had to periodically check twitter :\. There was no blog post, no status page I could check - my only hope was some unlucky dev I found that didn't even work on the iTunes Connect/App Submission team.

I think the consensus is that we need nothing but bug fixes on the core stuff (Xcode, SourceKit, etc).

indeed. i think apple has a general software quality issue and should now think about hiring some senior devs from microsoft to help them sort their process out.

how big is this decent size codebase?

397 Swift files, 2K Obj-C.