The article analyzes the three‑year Rust rewrite movement, presenting concrete performance gains, binary‑size challenges, new bugs, learning‑curve costs, and real‑world cases of both success and abandonment to help developers decide whether a Rust rewrite is worthwhile.
The author, a veteran Java and C# developer, outlines seven practical reasons—faster development, rapid builds, consistent code style, tiny Docker images, a rich standard library, lightweight goroutines, and a simple web server—that convinced him to abandon Java and C# for Go, boosting productivity.
This article details the Alipay Tech team's systematic approach to reducing Kotlin/Native binary size for Android, iOS, and HarmonyOS by tuning compiler parameters, leveraging LLVM optimization passes, and applying fine‑grained export and dead‑code‑elimination strategies, complete with test methods and measurable results.
Discover practical techniques to dramatically reduce the size of Go executables—starting with stripping debug symbols using ldflags, then applying UPX compression with optimal settings, and combining both methods to shrink a 6.5 MB binary down to around 1.4 MB, saving up to 80% space.
This article explains Go’s dead code elimination (DCE) optimization, demonstrates it with sample code, shows how to inspect compiled binaries using go tool nm, and discusses factors that affect DCE such as code complexity, compiler flags, and reflection, helping developers reduce binary size.
Version 1.41 of the Deno runtime, released on February 23, reduces compiled binary sizes by up to 50%, introduces official Linux ARM64 binaries, adds several Node.js compatibility fixes, expands API capabilities, and improves language server features, while outlining future plans for further size reductions and custom builds.
Learn how Go’s embedded symbol table works, how to inspect and modify symbols using tools like nm and go tool nm, customize variables with ‑ldflags ‑X, and reduce binary size by stripping debug symbols, all illustrated with practical code examples.
The article explains how iOS engineers keep the __TEXT segment under Apple’s strict size limits by removing unused code, using Link Map analysis, applying a custom SizeLine metric, and adopting coding practices such as limiting blocks, macros, and hard‑coded strings, all supported by automated monitoring and feedback.
