> I would think games don’t spend most of their time calling into networking code. Exactly. That is why the out-of-date networking example being touted as evid

> I would think games don’t spend most of their time calling into networking code. Exactly. That is why the out-of-date networking example being touted as evidence is irrelevant here. What it boils down to is that Java and C have fundamentally incompatible memory models. Direct access to C memory is impossible because of the managed heap and GC. > I would take this bet that it won’t. Purely on the sheer fact that gaming occurs on Windows and Swift is barely capable there. This is a very odd comment - gaming occurs in a lot of places. Quite a lot happens on mobile these days. Turns out a lot of mobile devices run Swift, on which it appears to be reasonably capable.