The author compares Rust and Swift, highlighting their similarities and differences. Both languages borrow features from functional programming, such as tagged enums and pattern matching. Rust is a low-level systems language that emphasizes performance and memory safety through a strict ownership model, while Swift is a higher-level language designed for simplicity and ease of use. Swift defaults to value types with copy-on-write semantics, making it easier for developers to manage memory without delving into the complexities that Rust requires, like wrapping values with `Cow<>`. Swift's syntax often mirrors C-like constructs, which can obscure its more functional features. For example, its `switch` statement acts like Rust's `match` but with a familiar look. Similarly, Swift's handling of optional types (`T?` instead of Rust's `Option<T>`) provides convenience, as it implicitly manages nil checks. Error handling in Swift also mirrors Rust's `Result` type but does so in a way that feels more approachable for developers used to traditional exception handling. The author notes that Rust's compiler catches more issues at compile time, forcing developers to confront problems directly, like self-referencing enums. In contrast, Swift's compiler automates some of these concerns, making it easier to write code but potentially less explicit. Swift's design choices, influenced by its goal to replace Objective-C, result in a larger feature set that includes classes, async-await, and property wrappers. While Swift is easier to learn and use, it sacrifices some performance—Rust is generally faster out of the box. Finally, the article addresses the evolving perception of Swift as primarily an Apple-centric language. Swift is increasingly cross-platform, with support for Windows, Linux, and even web assembly (WASM). The development of Swift for embedded systems shows its growing versatility. As projects like the Arc browser and server-side Swift gain traction, Swift's interoperability becomes a significant advantage, challenging the notion that it belongs solely to the Apple ecosystem.