Strange. Apple makes the best products
For whom? By what standards?
They make some very good products and have a consistent and effective design language but they are as much a fashion company now as a technology one.
Dan East is not correct, time and distance are fundamentally the same thing
Well, maybe they're not exactly the same, but to say they are fundamentally different is a bit of a troll for somewhere like slashdot? The interviews are interesting and well worth watching anyway.
Also, whoever does finally break two hours is going to be an outlier on all of the charts, so looking at averages of statistical samples isn't going to help.
For example in my own case: I'm 49 and I ran 2:57 this year, which puts me in the top 2.5% overall and 1% for my age. For me to run my best I need a day temperature of around 60F so I'm way off that particular chart.
I also disagree with the idea that a flat course is necessarily the fastest. Of course you don't want mountains, but some small changes of gradient can allow changes in muscle usage leading to reduction of fatigue. I've run both Hamburg and Berlin several times; I find the slightly more undulating Hamburg to be noticably easier than Berlin.
What the test shows is that most phones will resist a reasonable amount of bending when the load is applied uniformly at the centre. They all do pretty well. That's great.
The issue with the iPhone 6 Plus is that it has a weak corner, if you watch the 'bendgate' video you can clearly see that the bend line is not straight across the phone, but at an angle near to the weak spot.
A properly designed test would have clamped each phone flat with a corner sticking out unsupported and force applied until it suffered plastic deformation (stays bent). Each phone could have all four corners tested and the weakest result is the 'winner'. In such a test the iPhone 6 Plus would clearly fail at its weak point much more readily than any of the others.
I didn't say I haven't used obj-C, just not much, not recently and really only to experiment to see if it would be a good choice to use for my particular Python/Fortran based project. It was the Python bindings that made me take a look and I particularly liked how I could use dynamic typing and garbage collection, making it a good 'fit'. I was amazed by the quality of the Apple developer tools too.
The point I should have made was partly made by others later, namely that obj-C is well established and integrated in the toolchain and since all the frameworks are written in it it makes sense to choose it as his first language. Not to say that he should ignore Swift, but to leave it until he's got obj-C nailed.