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.
Bad science.
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.
With Microsoft now owning the Nokia phones, they can potentially have the same control over firmware updates as Apple, which leaves HTC and the others at a disadvantage whichever OS they use.
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn