3 ms·
It's also incorrect; he says he started it about four years ago, though it was just him for a while. > It's a "why-bother?" language rather than a "ack, no!" l
by rsynnott 12y ago
It's also incorrect; he says he started it about four years ago, though it was just him for a while.
> It's a "why-bother?" language rather than a "ack, no!" language.
The thing is, what is the alternative? They needed easy ObjC interoperability (all the APIs and third party libraries are in ObjC, and will be for a long time), and thus a compatible object model. That would knock out most alternatives on its own. Even if they were willing to compromise on that, and go with more heavy-weight interop, they'd basically be looking at adopting Rust, which isn't finished, or maybe D.
EDIT: On the age thing, by the way, it's also reasonably clear that Swift isn't finished. It should be usable by the time Xcode 6 goes out of beta, but ObjC isn't going anywhere anytime soon, and I expect Swift will continue to evolve for a while yet.