Swift is a long way from Rust There is no memory model, really, from the POV of a Swift programmer. There are no guarantees about the cost of abstractions. T

Swift is a long way from Rust There is no memory model, really, from the POV of a Swift programmer. There are no guarantees about the cost of abstractions. The threading model is awful. Almost useless. I works well for simple cases (which are simple!) and not at all for complex cases. There must be a way for threads to communicate and synchronise other than a semaphore, but I have not found it. (Do not need it - keeping it simple and on one thread). The compiler is very slow. You thought the Rust compiler was slow? Try Swift! Not Swift, but the IDE provided by Apple cannot deal well with programmes when they approach ~100k lines. It gets very slow and its tools become unreliable. The learning curve of Rust makes it unsuitable for general purpose computing, and there is nothing hard about learning Swift. It has a lot of modern features (c/f C, my first love!) - map, reduce, optionals, result types, generics.... I do not think it is a threat to Rust for system programming outside of Apple (Dog knows what madness they will try). I think it's main competitor is Go. Not in systems programming but in general purpose computing.