4 ms·

What part are you responding to? I in no way made any claims about objc versus swift performance. I said the way they have tried to address memory safety assume

• mpweiher 3y ago
  "If it’s generally too hard for compiler people to optimize for the common case then it will be harder for folks to build great software." The compiler people don't need to optimise for the common case.
  • zer0zzz 3y ago
    That’s literally all compiler people do.. if we see a pattern people are using 80 percent of the time we find a way to make it better. There are ways to make ObjC better optimized at the compiler and runtime level but no one is exactly asking for patches for doing so for objc for very obvious reasons (which I am not going to discuss on a public forum).
    • mpweiher 3y ago
      > That’s literally all compiler people do. I know. My point is that in lots of cases it is unnecessary and in fact unhelpful. > make it better Well, you first need to get agreement from your language users on what constitutes "better". Removing the dynamism from a dynamic language does not make it "better".
      • zer0zzz 3y ago
        > Well, you first need to get agreement from your language users on what constitutes "better". Removing the dynamism from a dynamic language does not make it "better". I think that depends on if said dynamism is being intentionally used. Far too often it is not, and it gets even worse when that is paired with tools that do automated source code generation like the kinds Meta and Google use (or misuse depending on your definition).