This is particularly relevant right now. The swift-evolution mailing list is currently discussing adding a "dynamic member lookup" protocol to Swift to enhance interop with dynamic languages like Python, Ruby, and Perl. You can see the proposal here[0].<p>[0] <a href="https://gist.github.com/lattner/b016e1cf86c43732c8d82f90e5ae5438" rel="nofollow">https://gist.github.com/lattner/b016e1cf86c43732c8d82f90e5ae...</a>
I still like Objective-C even if it isn't my go-to language anymore. It's quite elegant compared to it's peers from the 80's, it's a very small language yet you can achieve everything with it, even if it means dipping into C(++) for the parts that need to be really performant. But on the other hand seeing a different programming language when there's some optimization going on and having another programming language for business logic is a great thing too.<p>How many times don't we see bugs, errors or security issues stemming from the fact that business logic gets implemented in C?
I'm getting the loading error, "An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details."<p>Not sure if there is a mirror, a write-up, or another example anyone might be able to pass along.<p>edit: this google cache version is working[0].<p>[0] <a href="https://webcache.googleusercontent.com/search?q=cache:gXiqzW0OV04J:https://academy.realm.io/posts/mobilization-roy-marmelstein-objective-c-runtime-swift-dynamic+&cd=1&hl=en&ct=clnk&gl=us&lr=lang_de%7Clang_en" rel="nofollow">https://webcache.googleusercontent.com/search?q=cache:gXiqzW...</a>
<i>> Before we start, Objective-C is a runtime-oriented language, which means that all of the links between your methods and variables and classes are deferred to the last moment possible to when your app is actually running, and this gives you great flexibility because you can change those links. The alternative, where Swift is most of the time, is compiletime-oriented languages. So in Swift everything is a bit more harder bound, and you get more safety, but it’s less flexible.</i><p><i>> This is what this debate was all about.</i><p>Not just <i>safety</i>, but also performance. Swift offers significant performance gains when you don’t need the dynamism. Swift lets you opt into dynamic features (as he later explains), and you can seemlessly interact with Objective C on Mac platforms. But you don’t have to pay the penalty for dynamism in the vast majority of your code that doesn’t use these features.<p>Edited: I also pointed out some additional mistakes in the post, but removed that because this comment got too long.
>"Before we start, Objective-C is a runtime-oriented language, which means that all of the links between your methods and variables and classes are deferred to the last moment possible to when your app is actually running, ..."<p>I had not heard the term "runtime-oriented language" before. Is this really just another term for "supports reflection"? If not what would be other examples of "runtime-oriented" languages?