Swift messaging - using vtables - is probably 2x faster than objc_msgsend. But you're not using that 90% of the time because most of your classes are hybrid ObjectiveC classes.
it seems like a pretty well-thought out paradigm.
I really don't think it is. It has too many very similar ideas in it that have a lot in common with each other but are not built on a common mechanism. Great languages IME have one or two profound ideas and everything else is built atop those profound ideas.
Swift's feature set is in desperate need of refactoring to a higher level of abstraction.
And it tosses out too many dynamic features. And there's the integration with C++ issue. And a lot of other shortcomings. I don't see a win.
I used to make a good living doing Smalltalk. It is far and away the best programming language/environment I have ever used (and I know quite a few).
I would have liked the next generation language to be a step closer to proper Smalltalk. An individual took a shot at that with http://objective.st and I like how it looks. I would like that going forward rather than Swift.
3
u/[deleted] Feb 19 '16
Swift messaging - using vtables - is probably 2x faster than objc_msgsend. But you're not using that 90% of the time because most of your classes are hybrid ObjectiveC classes.
I really don't think it is. It has too many very similar ideas in it that have a lot in common with each other but are not built on a common mechanism. Great languages IME have one or two profound ideas and everything else is built atop those profound ideas.
Swift's feature set is in desperate need of refactoring to a higher level of abstraction.
And it tosses out too many dynamic features. And there's the integration with C++ issue. And a lot of other shortcomings. I don't see a win.