When I started writing iOS Apps it was at the same time as Interface Builder was released.
As a beginner being able to visualise what was going on made the learning curve a walk up a hill instead of mountaineering.
Even though I've been doing it a while now I still use Storyboards but 50% of the time I find myself removing a view and codifying it.
As a design tool it is wonderful for prototyping.
There was a lot of resistance from the established iOS developers to IB when it first appeared.
I remember being scolded on stockoverflow for using IB and told that I should learn the hard way like they had done.
With Swift I see some parallels, I don't want to have to learn a new language even though it might be simpler and compiles faster code (allegedly).
It raise my hackles because of the time and knowledge I have invested in the status quo to date (ObjC).
In addition to the prospect of Apple ceasing support for ObjC in future Xcode releases forcing me to re-write my Apps in Swift.
I'm sure Swift will make the learning curve easier as IB did for me when I started.
There's a much bigger problem with all this which goes beyond Apple, Xcode & Swift.
As App development and programming becomes simpler and more dumbed down it has the effect of increasing the number of people who are capable of producing a non-complex App.
That drives down the value of an App developer.
It's hard enough making anything from App's without lowering the value in them further.