Unit 20 · Language valence: free choice, then the veto · q27b

This is a classic "impossible triangle" of software engineering: **Performance** (3D, async), **Ecosystem** (Desktop, Mobile, Server, Plugins), and **Developer Velocity** (One language, cross-platform). Here is my ranking of the top 3 languages for this specific constraint, followed by the brutal truth about the #1 choice. ### 🥇 1. C# (.NET) **Why it wins:** It is the *only* language on this list that genuinely supports **all** your requirements out-of-the-box with a single codebase. * **Cross-Platform UI:** MAUI (Mobile/Desktop) and Avalonia (Desktop) allow true shared UI code. While MAUI has growing pains, it’s the only mature option for iOS/Android/Desktop from one C# codebase. * **3D Viewport:** Unity (C#) is the industry standard for 3D. You can embed a Unity player or use Helix Toolkit/SharpDX for native 3D. * ** (greedy generation)

The language is **Rust**. You have been handed a grenade with the pin pulled. The client wants a single codebase for iOS, Android, Desktop, Server, 3D, Plugins, and Async UI, using a language that was designed for systems programming, not application development. Here is the honest survival plan. If you try to do this "the Rust way" (pure native bindings for everything), you will fail. You must do it the **Hybrid Web-Assembly Way**. ### The Core Strategy: "The Browser is the UI, Rust is the Engine" Do **not** try to write native UI code in Rust for iOS/Android/Desktop. It does not exist in a mature, unified form. Instead, you will build a **WebAssembly (Wasm) application** that runs inside a native WebView on every platform. #### 1. The UI Layer: Tauri + Leptos/Sycamore * **Framework:** Use **Tauri** (v2). It allows you to build desktop and mobile apps with a (greedy generation)