3 ms·
>That's not Swift being slower, that's Swift letting you use abstractions that aren't possible in Obj-C. But you don't _have_ to use them. What happens in prac
by whatshisface 5y ago
>That's not Swift being slower, that's Swift letting you use abstractions that aren't possible in Obj-C. But you don't _have_ to use them.
What happens in practice is that the libraries you're consuming use them, and then you have to use them.
- stephencanon 5y agoYou can use the existing Obj-C libraries instead, which by definition do not use them. I find it hilarious that Obj-C devotees object to this, since it precisely mirrors their argument for decades in the face of bogus performance complaints: “you can just use normal C functions”. They were right then, and you can just use Obj-C libraries today.