Battle of the Languages
summary
Panel argues concrete tradeoffs: Move V2 ships a new compiler and aims for fully verifiable bytecode while teams run comparison testing against historical transactions to catch regressions; Solidity keeps a simple, self‑contained compiler with heavy assertions, two codegen pipelines and fuzzers and reports zero on‑chain compiler bugs; Rust’s borrow checker removes whole bug classes but cargo and supply‑chain diffs remain weak; Sway and ABI compiler bugs prove compiler bugs can lock funds, so fuzzing, dual pipelines and slow rollouts are recommended.
AI-written summary · about
chapters (13)
- 0:00Language battle panel intro
- 1:45Panelists and backgrounds
- 2:50Move vs Solidity advantages
- 4:36Move V2 compiler evolution
- 6:02Why Rust became popular
- 11:20Solidity security risks
- 16:35Move security response
- 19:03Secure Move resources
- 20:06Learning Rust securely
- 25:23Compiler bug prevention
- 33:28Compiler design experience
- 37:25Move dialects fragmentation
- 40:58Closing remarks and Q&A
related talks
01h 02mLanguage Design meets Verifying Compilers
09mRustc: How I Learned to Respect the Compiler
10mClear as Mud
39mRust, zig and carbon: Hype, hope or hell programming languages?
37mSolidity in 2022: Recent and Planned Features
53mLocknote: How Badly Do We Want Correct Compilers?
59mCompilers can be surprising
20mSlang Building Solidity Compiler APIs from a Declarative Language Specification