Facing a 24‑million‑line codebase with over 100 third‑party pods, the team tackled slow Xcode compilation, lengthy packaging, and merge‑request bottlenecks by applying build‑setting tweaks, RAM‑disk compilation, CCache, and a custom binary‑pod workflow that automates packaging, publishing, and integration without altering source projects.
Savitar, a custom Android Studio plugin suite, accelerates incremental compilation by detecting changed files with Watchman, gathering project metadata, invoking javac/kotlinc and AAPT2 for on‑demand builds, and hot‑loading Dex and resources at runtime, cutting average incremental build time from 110 seconds to 15 seconds and saving thousands of developer hours.
This article examines current iOS modularization using CocoaPods, explains binary pod strategies to dramatically reduce build times, compares manual and automated approaches, addresses debugging challenges, and presents a practical solution that toggles between source and binary modes via environment variables and Development Pods for flexible development and fast CI builds.
This article describes how the author reduced a multi‑project frontend application's webpack build time by over 60% through dynamic entry configuration, environment‑variable driven builds, and caching of expensive loaders, providing code examples and performance results.
Youzan’s EnjoyDependence Gradle plugin dramatically speeds Android full builds—cutting compilation of their 450K‑line, Kotlin‑heavy project from over 15 minutes to under three—by managing dependencies, publishing AARs, and swapping source modules with prebuilt artifacts without altering project structure, while remaining stable and easy to adopt.
This article explains how to enable TypeScript’s incremental compilation feature in a Midway project by adding the "incremental": true option to tsconfig.json, demonstrates the resulting tsconfig.tsbuildinfo file, shows faster subsequent builds, and introduces the new createIncrementalProgram API introduced in TypeScript 3.6 for programmatic incremental builds.
This article explains the drawbacks of using a vendor directory in Go projects, outlines how Go module proxy solves those issues, and provides step‑by‑step guidance on configuring GOPROXY, choosing public or self‑hosted proxies, and recent Go 1.13 enhancements.
This article examines how Baidu App’s massive iOS codebase was streamlined with the EasyBox toolchain, detailing component management, multi‑repo handling, compile isolation, binary distribution, and performance optimizations that reduced full builds from twenty minutes to under two minutes.
This article describes how the Smart Train Ticket Android team adopted a componentization architecture—splitting base libraries and business modules, configuring independent and integrated builds, handling inter‑module communication, and solving manifest and multi‑flavor packaging challenges—to reduce coupling and dramatically improve build performance.
The article details how to reconstruct Xianyu’s product detail page using Flutter within existing native iOS/Android apps, covering project structure, environment management, build optimizations for Android and iOS, native‑launch debugging with hot‑reload, and CI integration for reliable hybrid releases.
This article provides a comprehensive overview of web performance optimization for frontend developers, covering metrics and goal setting, code and DOM optimizations, static asset compression, delivery techniques like async loading and resource hints, build strategies such as tree‑shaking and SSR, and monitoring tools.
Meituan Dianping’s Mobile Continuous Integration (MCI) architecture tackles tangled component dependencies, fragmented workflows, and long build times by combining GitLab‑based CI pipelines, dependency flattening, binary integration with multi‑threaded caching, a custom static‑analysis framework, comprehensive logging, monitoring, and a centralized configuration portal, achieving roughly 60 % faster iOS builds and 50 % faster Android builds.
This article details the design and implementation of Tencent Cloud's internal YY‑DSA operations platform, covering project background, frontend technology selection (Vue.js, Element‑UI, webpack), project structure, development environment, build optimizations such as code splitting, CommonsChunk, and the comparison of Dll versus externals for faster builds.
Long‑running projects inevitably see their initial excitement with new frameworks fade as codebases grow, builds slow, and teams expand, leading to architectural decay; this article explains the causes, stages, and practical strategies—such as modularization, progressive builds, and disciplined technology adoption—to mitigate the problem.
The article explains how long‑running software projects inevitably suffer architectural decay due to growing codebases, slower builds, and team turnover, and presents practical strategies such as environment upgrades, staged and distributed builds, modular isolation, and platform‑plus‑app designs to keep systems sustainable.
The article discusses practical solutions for long C++ build times, introduces a company‑wide compile cluster with a localbuild.sh script, outlines how developers can run automated tests, defines testing strategies, sets criteria for feature readiness, and presents approaches to performance testing and estimation adjustments within a CI‑driven development workflow.
This article examines why long‑running software projects experience architectural decay, the limitations of new frameworks, and presents practical solutions such as environment upgrades, phased and distributed builds, refactoring into isolated components, and adopting modular, loosely‑coupled platform‑plus‑application designs to sustain development productivity.
Learn how to dramatically reduce webpack build times for large React projects by switching to Yarn, removing unused dependencies, leveraging code splitting, caching, parallel Uglify, HappyPack, DLL plugins, aliasing, and other practical configuration tweaks that cut initial builds from minutes to seconds.
The article examines why long‑running software projects inevitably suffer architectural decay, explains how growth in code, team size, and build complexity erodes productivity, and presents practical strategies—including environment upgrades, phased and distributed builds, component isolation, and adopting new technologies—to slow or reverse the decay.
Learn how to leverage webpack 2's advanced features—such as CSS minification, tree‑shaking, UglifyJsPlugin tuning, environment variables, CommonsChunkPlugin, and development‑time accelerators like aliasing and caching—to produce smaller bundles, faster builds, and a smoother developer experience.
This article introduces HappyPack—a webpack plugin that speeds up builds by running loaders in parallel processes—covers its configuration, internal architecture including thread‑pool management, RPC handling, caching mechanisms, and provides detailed code examples to illustrate its integration and operation.
The article explains how Facebook’s Buck build tool accelerates Android development by leveraging fine‑grained parallelism and an O(NlogN) DexMerge, delivering up to 40% faster full builds than Gradle, while covering its architecture, installation, K歌 project implementation, and integration challenges such as manual dependencies and Windows support.
This guide explains how to accelerate software builds on Linux by using make -j for parallel compilation, mounting a tmpfs for faster I/O, leveraging ccache to reuse previous compile results, and employing distcc to distribute compilation across multiple machines.
The article examines why software architectures inevitably degrade over time in long‑running projects, analyzes the stages of decay, and presents practical strategies—including environment upgrades, phased and distributed builds, component isolation, and platform‑plus‑app designs—to keep systems maintainable and performant.
This article explains how Ctrip’s Android app adopted a plugin‑based, dynamic‑loading framework to overcome method‑limit, improve build speed, enable hot‑deployment, and support modular A/B testing, detailing the underlying principles, compilation changes, runtime resource and class loading, and the trade‑offs involved.
The article examines why long‑running software projects inevitably see their architectures degrade, explores the stages of decay, and presents practical strategies—such as environment upgrades, phased and distributed builds, tooling, modular refactoring, and process isolation—to mitigate the problem.
The article analyzes how long‑running software projects inevitably suffer architectural decay due to growing codebases, team size, and build complexity, and proposes practical strategies such as modularization, phased and distributed builds, component isolation, and disciplined technology adoption to keep systems sustainable.