2 ms·
I'm not sure what's Apple plan here, as others have stated Swift will stay for the foreseeable future 'IOS language', and even if it is used internally, why not
by KolmogorovComp 2y ago
I'm not sure what's Apple plan here, as others have stated Swift will stay for the foreseeable future 'IOS language', and even if it is used internally, why not use Rust instead who provides a similar kind of safety and convenience, and is already much more used in embedded devices? Assuming the reason is to avoid using C/Cpp.
Given engineers' skills at Apple using Rust would not be an issue.
- steveklabnik 2y agoApple is using Rust internally for some things, but we don't know a lot about it. The most public info we have is job openings they've had.
- mannuch 2y agoRust is much less ergonomic than Swift, especially for application-level development. I like to think about it like this: Rust forces you to think about memory where Swift doesn’t. But what’s really cool is that Swift is adopting some of the great things about Rust’s ownership system, allowing you to “opt-in” to a Rust-style performance profile if you think the mental overhead is worth it for your use-case or domain. To see what I’m talking about check out https://youtu.be/I9XGyizHxmU?si=Zl-7dA0NqhnctRPQ https://youtu.be/I9XGyizHxmU?si=Zl-7dA0NqhnctRPQ What’s exciting to me is that Swift is becoming a great language that works at all levels of the stack while staying a language that feels really great to write. IMO what’s largely held it back in adoption is its cross-platform experience, but you see that the Swift team is really trying to change the perception here (they’ve specifically tried to highlight using non-Xcode/non-Mac dev environments, deploying to Linux, developing embedded etc.).