> Swift doesn't have a separate processes managing memory during the runtime Plenty of GCs don't have this. You can have cycle collectors and other GCs which r

> Swift doesn't have a separate processes managing memory during the runtime Plenty of GCs don't have this. You can have cycle collectors and other GCs which run the GC pass on release events (depending on some heuristic) too. This is a terminology issue, anyway -- in academia reference counting is considered a form of GC. In software often the term is used to mean "tracing GC", or sometimes "any system that can automatically handle retain cycles". ----- This still doesn't answer why Swift has a wider range of possible applications, though. I do agree that Swift is or will be better suited for development on iOS, because of good API integration. Rust can program for iOS too, it's just that you will have better support for Swift :) But aside from that, Rust should be able to apply anywhere Swift does.