Android phones bend too.

As anyone could have found with Google before they tried to make this a thing about Apple.

Just be aware and it'll be fine, with any phone.

They denied many people had them but eventually fixed it anyway with a free bumper.

That didn't *fix* anything though. As was widely reported at the time, ALL phones lose signal dramatically with a death grip, iPhone or no, even with a case.

I never used a case or bumper with the "Antenna phone" and need had an issue dropping calls.

The free bumper was just PR.

I imagine somewhere in Apple's labs they are testing strengthened cases

Possibly, but I think that will only come into play with the iPhone 6s. I'm sure they will consider it more strongly.

The first mission or two is probably no return anyway so who cares if you can't abort?

I'd still sign on in a heartbeat.

We need to be WAY less cautious about manned space travel again, we aren't going to do much of import at this pace.

Exactly! Glad someone understands.

I'm basically someone who knows what he likes and is also not stupid enough to tie myself to a single party mindset or outlook, instead over time I've learned to think for myself.

It will slowly gain traction among iOS developers, and some will use it for new code, but that doesn't mean it will be dominant by any means.

I don't think you understand, for new projects it pretty much already is.

The fact remains that there are billions of lines of Objective-C code out there. If you honestly think that developers are going to rewrite all those billions of lines of code

Of course not but over time refactoring will rid you of much of that.

I'm not saying all of that is going to be re-written, but within a year I don't think many projects will be started that do not use Swift at the outset.

Now if Apple were to release an Objective-C to Swift translator,

In effect they already do by automatically generating Swift versions of any header files you want Swift to see. That means it's zero cost to call into any existing code from Swift.

If anything, they're usually not cynical enough to adequately model developer apathy and resistance to change..../em

You REALLY do not understand the iOS development community. I would agree with you in any other context, I have been a developer in a lot of worlds, from backend to front end dev. In any other community of developers you would be right; for iOS development you are so, so wrong - primarily because iOS developers are used to constant change anyway, the language changing is just one more change. If it makes you even a little more productive people will use it - and Swift does that quite well.

My predictions are also very, very conservative...

I wouldn't ever carry a bare phone or one with just a silicone bumper in a front pocket

I have for years without issue.

And that includes the iPhone plus.

Theres simply not enough force to even come close to flexing the phone, much less bending...

Back pockets are I think more worrisome but even there - the Plus (as the tests show) is pretty damn rigid.

70 lbs is easy to bend just moving around in tight pants

Perhaps if you are the Hulk, unlike you I wear a phone AND PANTS all the time and I can verify no such forces are exerted from normal wear (and that includes Jeans which are the Iron Maiden of phone holders).

Executive summary: MONEY GOOD

Summary for everyone else: I have a Plus in my pocket and looking at what should get bent soon, pretty sure it's you,

So, if the phones are bending in real world situations, they are by definition defective

Except they aren't.

Apple sold 10 *million* phones over the weekend. Of those, Apple says they have six complaints. And we haven't seen that many pictures from real owners.

So the reality is that the iPhone 6 is not defective, a few have undergone more extreme forces than is reasonable. In the end a large flat object can be broken, that's just physics and no amount of design will change that.

If you plan to put ANY phone through more extreme forces than normal, get an Otterbox and call it a day.

If they only test the phone on the middle, what's the point?

A) Most people with phones in the back pocket would have strain excerpted roughly from the middle, not some offset point.

B) With the 6 Plus the distance from the center to the volume buttons is so small I doubt there would be any change in the results. Forces distributed across the device find the weakest point even if it is offset.

but the 6 bends at nearly HALF the pressure of the 5

Neither figure matters if the pressure actually put on the phone in your pocket is 1/10th of 55 lbs.

To phrase it differently since you seem to have a personality tailor-made for being "misled by statistics", if the only force a device undergoes is 10-20lbs, why does it matter if a device can sustain a million pounds of force, or 30,

Remember that in realty Apple's has reports of just six actual phones being bent.

I have a 6plus and have been using it in my pocket. After sitting or leaning over or whatever, there is zero bend or even flex to the thing. To actually bend it would take enough force I'd be concerned about my own structural integrity.

Strawman. At least some of the reports of bending were from people claiming they put the phones in their front pockets.

Well hello, Counter Strawman.

In reality the 6 plus works fine in front pockets - I know. I've been using it for days and there's not even a hint of bending from having the phone in your pockets.

Furthermore that was the point of the tests consumer reviews did, under normal packet use these things are not going to bend - especially in front pockets.

Swift on the other hand hasn't been out long enough for there to be enough answers on the knowledge base websites to cover all issues that will arise in the learning curve.

Between Apple's excellent free books and StackOverflow (which is brimming with Swift questions and answers) that is not at all true. Any issue you run into coding Swift is well covered by online resources already.

Remember how long it took to lay Carbon to rest.

Carbon was an entirely different set of frameworks.

Swift on the other hand uses all of the existing frameworks - only the have tweaked the Swift definition of the endpoints such that it's more Swift friendly (like knowing when arguments or return values will or will not be null for sure).

So there is zero Carbon-Like transition time involved.

I'm not drinking the Apple Kool-Aid, I am telling you what is happening in real-world iOS development today. If you learn anything but Swift you are going to be WAY behind state of the art inside a year.

I'd say it's 50/50 whether or not Swift will get enough traction to continue on.

Jumping horny ghost toad of Fernando, you are not really that stupid, are you? Please tell me you are just trolling? You really don't understand what happens when Apple puts weight behind a development technology? Wow.

In one year I will re-link to your post in EVERY Slashdot post you make.

At this point I wouldn't even buy whatever CEREAL you normally buy, with judgement like that.

There's a very strong case to be made for Swift first going forward, and not many seem to be making it or understand the iOS dev world at all.

I speak as someone who has been developing iOS applications since somewhat before the release of the iOS SDK way back when.

I don't think anyone outside those paying the closest attention to iOS development realize how rapidly Swift is being adopted, especially by those who have been doing Objective-C the longest.

That's the core aspect of this I don't think people understand. iOS developers by and large are a very pragmatic bunch. Even those who love Objective-C (and there are many) are perfectly happy to move to something new that makes development even faster so they can accomplish the end goal of building apps for people.

That's really what iOS developers really care about, delivering apps. Anything that helps they are on-board with, and you can plainly see Apple is backing Swift big-time so the developers are hitching to that very powerful wagon.

If I were advising ANY developer new to iOS, I would absolutely say go Swift first. Someone said there's more Objective-C educational material? Technically true, but also consider how much of that is outdated. With Swift anything you find (and there is a LOT right now) is guaranteed fresh.

If you worry the iOS development market is overcrowded, don't - experienced developers for all backgrounds are badly needed all over.

Swift isn't finished. From what I've read, they expect to make syntax-incompatible changes.

That was before Swift 1.0 introduced with the final XCode 6 and iOS8. They aren't breaking syntax anymore...

And even when they were, it was usually pretty minor things to fix.

I'd imagine it will eventually (over a couple of decades)

HA HA HA HA HA HA HA

You don't know Apple, or iOS developers. Dominant over ObjC within two years (and by the end of next year that prediction will probably seem ridiculously conservative).