3 ms·
> I think that Swift is more interesting than Rust in some of the higher-level application demands, but we’ll see What does "higher-level application demands"
by twic 8y ago
> I think that Swift is more interesting than Rust in some of the higher-level application demands, but we’ll see
What does "higher-level application demands" mean?
- bluejekyll 8y agoI’m assuming they mean that Swift generally is easier to use with dynamic types than Rust. Rust has dynamic polymorphism like Swift, but Swift you opt-out with final (correct me please if I’m wrong here), whereas in Rust you need to promote to a trait object. This is a small difference, but means you’re starting with different principles available to you out of the box. Personally I prefer Rust’s opt-in to complexity model, but I can see why people see that as a hinderence, even if it’s technically just as possible to do in Rust.
- dep_b 8y agoExpressing business logic. Which is probably true (but I don’t have real Rust experience)
- pjmlp 8y agoThe memory management is more developer friendly and it doesn't get into the way like it still does in Rust, even with the upcoming NLL improvements, not all productivity use cases are covered, e.g. self referential references to fields in struct methods. Then there are Swift Playgrounds and REPL for quick prototyping and those still aren't a thing in Rust.