# build performance Software engineering concern of reducing the time needed to run software builds. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## ESPHome 2026.9.0: Faster builds and encrypted updates DevFeed: [ESPHome 2026.9.0: Faster builds and encrypted updates]() Original publisher: [Read original article]() Author: Jesse Hills Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [ESPHome - Smart Home Made Simple - Blog]() Topics: [esphome](), [PlatformIO](), [ESP8266](), [Encryption](), [build performance](), [ChaCha](), [toolchain](), [Home Assistant]() Tags: [2026](), [benchmarks](), [builds](), [ci](), [encryption](), [esp32](), [esp8266](), [esphome](), [ota](), [parallel](), [releases](), [toolchain](), [updates]() ### AI overview ESPHome 2026.9.0 improves build performance by parallelizing PlatformIO setup, lays groundwork for a native ESP8266 toolchain, adds Noise-encrypted OTA updates, and reduces ESP8266 RAM usage. The release also includes component additions, platform updates, and fixes. ### Source excerpt ESPHome 2026.9.0 parallelizes PlatformIO installs, lays the groundwork for a native ESP8266 toolchain, adds Noise-encrypted OTA updates, and frees ESP8266 RAM. ## C++ in the Age of AI: Visual Studio at CppCon 2026 DevFeed: [C++ in the Age of AI: Visual Studio at CppCon 2026]() Original publisher: [Read original article]() Author: Augustin Popa Published: 2026-09-14T19:34:43Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [C++](), [Visual Studio](), [GitHub Copilot](), [Visual Studio 2026](), [build performance](), [MSVC](), [debugging](), [Optimization](), [Refactoring](), [Artificial Intelligence]() Tags: [ai](), [build-optimization](), [build-performance](), [c-plus-plus](), [copilot](), [cppcon](), [debugging](), [github-copilot](), [msvc](), [visual-studio](), [visual-studio-2026]() ### AI overview This companion reading guide covers how Visual Studio 2026 is evolving C++ development with improved code navigation, build and runtime performance, language feature support, debugging, modernization, refactoring, and AI-assisted workflows using GitHub Copilot. ### Source excerpt At CppCon 2026, we shared how Visual Studio is evolving to help you work more effectively with large C++ codebases, improve build and runtime performance, adopt the latest language features, and incorporate AI into your existing workflows. This post is a companion reading guide for our session, C++ in the Age of AI: How Visual [...] The post C++ in the Age of AI: Visual Studio at CppCon 2026 appeared first on C++ Team Blog. ## Linux 7.4 Could End Up Seeing Kernel Builds ~36% Faster, Incremental Builds ~70% Faster DevFeed: [Linux 7.4 Could End Up Seeing Kernel Builds ~36% Faster, Incremental Builds ~70% Faster]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-14T10:31:16Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [build performance](), [build times](), [Arm](), [Compiler](), [Git](), [Artificial Intelligence]() Tags: [ai](), [arm](), [build-times](), [compiler](), [desktop-linux](), [git](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview A second revision of Linux kernel patches could make full allmodconfig builds about 36% faster and incremental builds about 70% faster. The work, led by Lorenzo Stoakes of Arm, addresses single-threaded bottlenecks and includes fixes, an upstream rebase, and an optional parallel Rust compiler front end. The patches are being considered for inclusion in Linux 7.4. ### Source excerpt Earlier this month I wrote about a patch series posted to the Linux kernel mailing list that addressed a lot of "hideous code" to make Linux kernel builds faster. A number of single-threaded bottlenecks were tracked down and fixed within the Linux kernel thanks to the assistance of AI. A second revision of those patches hit the mailing list this morning and there is hope they could be upstreamed for Linux 7.4... ## Migrating evilmartians.com from Gatsby to Astro in two weeks with Claude DevFeed: [Migrating evilmartians.com from Gatsby to Astro in two weeks with Claude]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Astro](), [gatsby](), [migration](), [Claude](), [Large Language Model](), [GraphQL](), [React](), [Security](), [build performance]() Tags: [ai](), [astro](), [build](), [claude](), [dx](), [graphql](), [javascript](), [migration](), [react](), [security](), [typescript]() ### AI overview Evil Martians describes migrating evilmartians.com from Gatsby to Astro in two weeks with Claude. The article outlines the site's Gatsby maintenance, security, and build-time costs, and discusses four bugs that could have shipped if the agent had operated without oversight. ### Source excerpt 367 posts, four years on Gatsby, and no dedicated team: here's how we moved evilmartians.com to Astro in two weeks with an LLM. ## Clearer Build Optimization Results with GitHub Copilot DevFeed: [Clearer Build Optimization Results with GitHub Copilot]() Original publisher: [Read original article]() Author: David Li Published: 2026-08-13T18:18:50Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [GitHub Copilot](), [Optimization](), [build performance](), [build times](), [C++](), [Windows](), [Visual Studio 2026]() Tags: [build-insights](), [build-optimization](), [build-performance](), [build-times](), [c-plus-plus](), [github-copilot](), [optimization](), [performance](), [visual-studio](), [visual-studio-2026](), [windows](), [workflow]() ### AI overview GitHub Copilot build performance for Windows now provides deterministic messages for optimization outcomes, including successful improvements, changes below the success threshold, unsuccessful changes, and builds that were too short to analyze. Successful results include baseline and final build times, measured improvement, and effects on iterative builds when applicable. ### Source excerpt We know that slow builds are a consistent theme in feedback from C++ developers. Your feedback helped us to shape GitHub Copilot build performance for Windows, an agent that can trace your build, find bottlenecks, apply optimizations, and measure the result. When using the agent, the clearest outcome is a straightforward win. The agent changes [...] The post Clearer Build Optimization Results with GitHub Copilot appeared first on C++ Team Blog. ## Dynamic Derivations + Dynamic build graphs: next steps DevFeed: [Dynamic Derivations + Dynamic build graphs: next steps]() Original publisher: [Read original article]() Author: tomberek Published: 2026-08-07T18:58:35Z Content type: opinion Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [build performance](), [systems](), [build times](), [bazel]() Tags: [announcements](), [bazel](), [build](), [ci](), [incremental](), [performant](), [ux]() ### AI overview A proposal for a Dynamic Derivations working group in the Nix ecosystem outlines collaboration goals, user-experience refinement, infrastructure needs, and adoption efforts. The post also summarizes the feature's development history and discusses potential benefits such as faster rebuilds and fine-grained incremental builds. ### Source excerpt After the long-history (see below) of Dynamic Derivations we are at a point where there are many groups exploring the feature and I am proposing a working group to: share the experiences of the implementors refine the user experience based on usage of the various PoCs determine infrastructure needs deduplicate work raise awareness build momentum for adoption ... anything else relevant I believe this feature has the potential to be a game-changer. Faster rebuilds, easier development, reduced pressure on CI systems, cacheable and alternative forms of instantiation, less need for "lang2nix", close the gap with Bazel, and fine-grained incremental builds. Along with the existing work on better schedulers, RBE-style remote builders, bytecode evaluation, parallel eval, memory optimizations (thanks @xokdvium !), and so much more - this is an exciting time for Nix and I can see DynDrvs as a way to fix some of the outstanding UX issues Nix has in day-to-day usage. There is even work to make IFD more performant, there is lots of design space to explore here. This should be a part of what Nix has to offer the world. @Ericson2314 has devoted years to this, and it deserves the payoff of becoming a mature feature. This is a call to action. Let's consider collaboration and a semimonthly meeting to at least say hello + consider next steps: Dynamic Derivations Working Group - Crab Fit History Dynamic Derivations have been in-progress for a long time. This has much of the history that I can put together. Let me know if this can be more complete. (and if anyone can help move/migrate into the wiki?) Build Systems à la Carte : 2018 RFC started Apr 2021 by @Ericson2314 and @L-as with [RFC 0092] Computed derivations by Ericson2314 - Pull Request #92 - NixOS/rfcs - GitHub (after reworking RFC 0040). Based on Initial example PoC by @L-as GitHub - L-as/nix-build.nix: nix-build.nix with RFC 92 - GitHub Content-addressed Nix Dec 2021: Implementing a content-addressed Nix by @thufschmitt. RFC Shep ## Real-Time CPU and Memory Insights for Harness CI Cloud Build DevFeed: [Real-Time CPU and Memory Insights for Harness CI Cloud Build]() Original publisher: [Read original article]() Author: Abhay Ganvir Published: 2026-06-17T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [ci](), [build performance](), [Cloud](), [cpu](), [IO](), [real-time]() Tags: [build](), [build-performance](), [ci](), [cloud](), [code](), [cpu](), [infrastructure](), [performance](), [real-time]() ### AI overview This article introduces CPU and Memory Insights for Harness CI Cloud builds. The feature collects CPU, memory, and disk I/O metrics from ephemeral build machines, streams them to the Harness platform in real time, and displays historical data to help teams right-size machines, investigate out-of-memory failures, and detect performance regressions. ### Source excerpt Get real-time CPU, memory, and disk I/O insights for Harness CI Cloud builds. Right-size machines, debug OOMs faster, detect regressions, and optimize CI performance with zero setup. | Blog ## Achieving Fast Inner Dev Loops with Gradle: Configuration Cache and Beyond DevFeed: [Achieving Fast Inner Dev Loops with Gradle: Configuration Cache and Beyond]() Original publisher: [Read original article]() Author: Alex Semin Published: 2026-05-20T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [code productivity](), [build performance](), [build times](), [Development]() Tags: [build](), [build-tool](), [compilation](), [context](), [developer-productivity](), [flow](), [gradle](), [incremental](), [kotlinconf](), [parallelism](), [productivity]() ### AI overview This article explains how Gradle is working to accelerate inner developer loops. It describes the shift from execution time to configuration time as the main build bottleneck in large codebases, while highlighting configuration cache, incremental builds, build cache, and parallelism as approaches to reduce waiting and preserve developer flow. ### Source excerpt How many engineers in your organization have to sit idle for 10 or more minutes just to rebuild the app locally after a small change? If you're an engineering leader, build engineer, or part of a developer productivity team, you're not alone in facing this challenge. Building complex software is inherently demanding, but the time your developers spend waiting has a profound impact beyond just the literal minutes lost. It fundamentally disrupts their psychological flow. "There are like these time scales of psychological flow, right? So if something takes longer than a minute, you already start planning for it... you suffer from context switch as well. If it's 1 second, that's where we want to be right in that seamless state of flow. And if it's less than one second, then you feel it's like magic... productive developers are happy developers." -- Rodrigo Oliveira When developers have to wait, their attention drifts, and the cost of context switching destroys their momentum. Our goal as enablers of developer productivity should be to eliminate this friction, bringing that feedback loop as close as possible to the "magical one second". In a recent presentation at KotlinConf 2025, Gradle engineers Rodrigo Oliveira and Alex Semin detailed how Gradle Build Tool is evolving to keep developers in that productive, happy "flow state". By tackling the most significant bottlenecks in modern software builds, Gradle is paving the way for incredibly fast inner developer loops. If you prefer to watch the presentation recording, you can find it here. The shifting bottleneck: From execution to configuration On every invocation, Gradle goes through three distinct phases: initialization, configuration, and execution. Historically, when we optimized Gradle builds, we focused almost exclusively on the execution phase. This is when the majority of work expected by a developer happens: production sources compilation, test execution, etc. For years, execution was the longest phase. We tackled thi ## Optimizing Our Build Times by Migrating from Webpack to Rspack DevFeed: [Optimizing Our Build Times by Migrating from Webpack to Rspack]() Original publisher: [Read original article]() Author: Benson Pan, Software Engineer Published: 2026-05-20T00:00:00Z Content type: tutorial Language: en Sources: [Yelp]() Topics: [Webpack](), [build times](), [monorepo](), [build performance](), [Developer experience]() Tags: [build](), [build-times](), [build-tools](), [developer-experience](), [migration-guide](), [monorepo](), [performance](), [speed](), [tooling](), [tools](), [webpack]() ### AI overview A Yelp engineering blog post explains how the team migrated monorepo builds from Webpack to Rspack. It reports an approximately 50% reduction in build time and discusses compatibility, configuration, custom plugins, and a staged rollout. ### Source excerpt Over the years, Webpack has remained the bundler of choice for many JS projects, including here at Yelp. While it has served us well, its speed has increasingly become a bottleneck as our monorepo continues to grow. Fortunately, a bunch of new build tools (Vite, Parcel, Rspack, etc.) have emerged in recent years. Each of these tools promises different ways of improving performance and developer experience. In this blog post, we'll walk through how we migrated our monorepo builds from Webpack to Rspack and achieved an approximately 50% reduction in build time. Why Rspack Our team has been closely observing... ## Supercharging Redpanda Streaming with profile-guided optimization DevFeed: [Supercharging Redpanda Streaming with profile-guided optimization]() Original publisher: [Read original article]() Author: Stephan Dollberg Published: 2026-04-02T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [Optimization](), [Streaming](), [Latency](), [Compiler](), [LLVM](), [Instrumentation](), [build performance](), [Benchmark]() Tags: [benchmark](), [bugs](), [compilation](), [engineering](), [instrumentation](), [latency](), [llvm](), [meta](), [optimization](), [performance](), [profile](), [profiling]() ### AI overview This article describes how Redpanda optimized its binary for Redpanda Streaming 26.1 using compiler-based profile-guided optimization (PGO) and LLVM BOLT. It explains how profiling data guides optimization decisions, compares the two approaches, and reports lower latency and CPU usage for intensive workloads. ### Source excerpt A behind-the-scenes look into how we optimized performance and cut latency in Redpanda 26.1 with profile-guided optimization. ## Jetpack Compose Hot Reload on Real Android Devices: Reduce the Build Time to Seconds DevFeed: [Jetpack Compose Hot Reload on Real Android Devices: Reduce the Build Time to Seconds]() Original publisher: [Read original article]() Author: Jaewoong Eum Published: 2026-03-31T02:51:42Z Content type: article Language: en Sources: [Stories by Jaewoong Eum on Medium]() Topics: [compose-hot-reload](), [Compose](), [Jetpack Compose](), [Android](), [Android Studio](), [Gradle](), [build performance]() Tags: [android](), [android-studio](), [build](), [compose](), [compose-hot-reload](), [compose-multiplatform](), [development](), [gradle](), [hot-reloading](), [jetpack-compose](), [kotlin-multiplatform](), [plugin](), [state]() ### AI overview This article introduces Compose HotSwan, a JetBrains IDE plugin for Android Studio and IntelliJ combined with a Gradle compiler plugin. It describes hot reloading Jetpack Compose code changes on physical Android devices and emulators in one to three seconds while preserving app state as much as possible, and explains the engineering constraints and capabilities involved. ### Source excerpt Upsplash@lenaborge In Jetpack Compose development, you are probably rebuilding your app tens of times per day to adjust the subtle design specifications. Each rebuild takes anywhere from 1 min to several minutes (~30 mins depending on your project scale), followed by navigating back to the screen you were working on and reconstructing the state you just lost for fair self-testing. Let's be honest. That adds up to one to two hours of dead time per day, every day, spent waiting instead of iterating. Well, for some, it's the perfect coffee break. For others, it's a frustrating blocker that slows everything down. That's exactly the problem Compose HotSwan is built to solve. Compose HotSwan is a JetBrains IDE plugin for Android Studio/IntelliJ and a Gradle compiler plugin that performs Jetpack Compose hot reload on real physical Android devices/emulators, applying code changes to a running app in one to three seconds with full state preservation as possible. In this article, you will explore what you can do with Compose HotSwan, the engineering constraints that make hot reload on Android difficult, how Compose HotSwan works within those constraints, and its core capabilities. The build tax: What slow feedback actually costs you Every Android developer knows the routine. You tweak a modifier, hit run, and wait. The build compiles, dexes, installs, and restarts your app. It launches from the home screen. You tap through multiple screens, scroll to the right position, and recreate the state just to see a one-line change. This is not just an inconvenience. It changes how you make decisions, and the cost compounds throughout your day. Picture this. You are working on a screen buried several layers deep. Everything is set up exactly where you need it. You change fontSize = 16.sp to 18.sp. Gradle starts building. On a small project, it takes a minute. On a large codebase, it takes much longer. The app reinstalls and restarts from the "home screen". All your state is gone. Now y ## App Hosting has in-console environment variables and faster builds DevFeed: [App Hosting has in-console environment variables and faster builds]() Original publisher: [Read original article]() Author: Julia Reid Published: 2026-03-12T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [hosting](), [build performance](), [configuration](), [Deployment]() Tags: [app-hosting](), [build-times](), [cloud-native](), [configuration](), [deployment](), [environment-variables](), [firebase](), [firebase-console](), [javascript](), [web]() ### AI overview Firebase App Hosting now supports adding and editing environment variables in the Firebase console. The update also describes configuration merging, precedence rules, secret references, and an optimized build process intended to improve build times. ### Source excerpt Manage environment variables in the Firebase console, and learn about a small change our engineering team made to improve build times for everyone. ## Why I'm Seeking Sponsors for Metro, a Kotlin Dependency Injection Compiler DevFeed: [Why I'm Seeking Sponsors for Metro, a Kotlin Dependency Injection Compiler]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-01-29T15:56:29Z Content type: opinion Language: en Sources: [Zac Sweers]() Topics: [Compiler](), [Dependency injection](), [build performance](), [build times](), [Kotlin](), [Mobile](), [monorepo]() Tags: [android](), [build-performance](), [build-times](), [compiler](), [dependency-injection](), [developer-productivity](), [kotlin](), [metro](), [monorepo](), [open-source]() ### AI overview The author discusses opening GitHub sponsorship for Metro, a Kotlin dependency injection project. They report build-performance gains, benchmark results against Dagger, compatibility across Kotlin and IDE versions, and adoption by several engineering teams. ### Source excerpt Metro is the proudest work of my career. Ever since starting it on vacation in November 2024, building it has been an incredible journey and the community reception has been nothing short of wonderful. It sits at the intersection of several fields I've come to specialize in, ranging ## Minimizing NixOS images DevFeed: [Minimizing NixOS images]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2025-10-21T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [gnu linux](), [build performance](), [iteration]() Tags: [article](), [build](), [capabilities](), [how-to](), [iteration]() ### AI overview Part two of a four-part series that explains how to reduce a NixOS appliance image from 1.5 GB to around 360 MB. It covers using Nix tools to inspect dependencies and applying configuration techniques to create smaller system images. ### Source excerpt Part 2 of our NixOS appliance image series - Learn how to use native Nix tools to shrink the size of your NixOS system images with quick iteration cycles! ## React Compiler v1.0 DevFeed: [React Compiler v1.0]() Original publisher: [Read original article]() Author: Lauren Tan, Joe Savona, and Mofei Zhang Published: 2025-10-07T00:00:00Z Content type: release Language: en Sources: [React Blog]() Topics: [Compiler](), [React](), [React Native](), [build performance](), [Expo](), [Next.js](), [Vite]() Tags: [2025](), [case-studies](), [compiler](), [meta](), [production](), [react](), [release](), [v1]() ### AI overview React Compiler 1.0 is released as the first stable version of a build-time compiler that automatically memoizes and optimizes React and React Native components and hooks without requiring rewrites. The release includes compiler-powered lint rules, an incremental adoption guide, and integrations intended to help new apps use the compiler with Expo, Vite, and Next.js. ### Source excerpt We are releasing the compiler's first stable release today. ## Optimizing Docker Image Builds for Size and Build Time DevFeed: [Optimizing Docker Image Builds for Size and Build Time]() Original publisher: [Read original article]() Author: Pranshu Raj Published: 2025-07-31T17:25:43Z Content type: tutorial Language: en Sources: [Pranshu Raj - blog on backend systems, performance and sidequests]() Topics: [Docker](), [Docker Image](), [Dockerfile](), [build performance](), [build times](), [Benchmark](), [Go Language]() Tags: [alpine](), [benchmark](), [build-performance](), [build-times](), [docker](), [docker-image](), [docker-image-size](), [go](), [how-to]() ### AI overview This tutorial describes optimizing a Go backend Docker image using Alpine base images and multi-stage builds. The reported changes reduced image size from 1.29 GB to 27.1 MB and build time from 43.8 seconds to 23.6 seconds. ### Source excerpt How to optimize (and benchmark) docker image builds for build time and image size. ## Vite 7.0 is out! DevFeed: [Vite 7.0 is out!]() Original publisher: [Read original article]() Author: The Vite Team Published: 2025-06-24T00:00:00Z Content type: release Language: en Sources: [Vite]() Topics: [Vite](), [Front end](), [JavaScript](), [toolchain](), [build performance](), [Open Source](), [Rust](), [Tooling]() Tags: [2025](), [announcement](), [blog-post](), [docs](), [frontend](), [javascript](), [migration-guide](), [release](), [rust](), [toolchain](), [vite]() ### AI overview Vite 7.0 is released with updates focused on the JavaScript frontend ecosystem. The announcement highlights Rolldown, a Rust-based bundler intended to become Vite's default and reduce build times, along with planned Vite DevTools for deeper debugging and analysis. ### Source excerpt Vite 7.0 is out! June 24, 2025 We're happy to share the release of Vite 7! It has been 5 years since Evan You sent the first commit to the Vite repo, and nobody could have predicted how much the frontend ecosystem would change since then. Most modern frontend frameworks and tools are now working together, building on top of Vite's shared infrastructure. And they can innovate at a faster pace by sharing at a higher level. Vite is now being downloaded 31 million times a week, with a 14 million increase in the last seven months since the previous major release. This year, we're making several big steps. To start with, ViteConf is going to be in person! The Vite Ecosystem will gather in Amsterdam on October 9-10! Organized by JSWorld in partnership with Bolt, VoidZero, and the Vite Core Team! We had three incredible ViteConf online editions, and we can't wait to meet in real life. Check out the speakers and get your ticket at the ViteConf site! And VoidZero continues to make significant strides in its mission to build an open source unified development toolchain for the JavaScript ecosystem. Over the last year, the VoidZero team has been working on Rolldown, a Rust-based next-generation bundler, as part of a broader effort to modernize Vite's core. You can try out the Rolldown-powered Vite today by using the rolldown-vite package instead of the default vite package. It is a drop-in replacement, as Rolldown will become the default bundler for Vite in the future. Switching should reduce your build time, especially for larger projects. Read more at the Rolldown-vite announcement blog post and our migration guide. Through a partnership between VoidZero and NuxtLabs, Anthony Fu is working on creating Vite DevTools. They will offer deeper and more insightful debugging and analysis for all Vite-based projects and frameworks. You can read more on the VoidZero and NuxtLabs join forces on Vite Devtools blog post. Quick links: Docs New Translation: فارسی Other Translations: 简体中文 ## Docusaurus 3.8 DevFeed: [Docusaurus 3.8]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2025-05-26T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [build performance](), [build times](), [Optimization](), [Cache](), [Webpack](), [Node.js](), [Netlify](), [Vercel](), [macOS]() Tags: [build-performance](), [builds](), [cache](), [macos](), [netlify](), [node-js](), [optimization](), [release](), [vercel]() ### AI overview Docusaurus 3.8 improves build performance through persistent caching, worker threads for static site generation, and other optimizations. The release also introduces Future Flags for preparing sites for Docusaurus 4 and adds new features. ### Source excerpt We are happy to announce Docusaurus 3.8. ## Next.js 15.3 DevFeed: [Next.js 15.3]() Original publisher: [Read original article]() Author: Will Binns-Smith Published: 2025-04-09T20:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [build performance](), [Instrumentation](), [Routing (disambiguation)](), [Caching](), [Webpack](), [Vercel]() Tags: [build-performance](), [build-times](), [caching](), [experimental](), [instrumentation](), [next-js](), [routing](), [typescript](), [vercel](), [webpack]() ### AI overview Next.js 15.3 introduces alpha support for Turbopack production builds, alongside client instrumentation and navigation hooks. The release also includes experimental Rspack community support and TypeScript plugin improvements. Turbopack is reported to outperform Webpack as CPU cores increase, while persistent caching remains experimental. ### Source excerpt Next.js 15.3 includes Turbopack for builds, new client instrumentation and navigation hooks, and more. ## Introducing Metro, a Kotlin compiler-plugin dependency injection framework DevFeed: [Introducing Metro, a Kotlin compiler-plugin dependency injection framework]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2025-04-03T16:14:23Z Content type: article Language: en Sources: [Zac Sweers]() Topics: [Dependency injection](), [Compiler](), [Kotlin](), [multiplatform](), [build performance](), [benchmarking]() Tags: [anvil](), [benchmarking](), [build-performance](), [compilation](), [compiler](), [dagger](), [dependency-injection](), [error-messages](), [kotlin](), [metro](), [multiplatform]() ### AI overview The article introduces Metro, a Kotlin compiler-plugin framework for compile-time dependency injection. It combines ideas from Dagger, Anvil, and Kotlin-Inject, and describes features including dependency graph validation, code generation, multiplatform support, IDE integration, and diagnostics. The author reports benchmarked build-time improvements in a CatchUp app and notes that Metro 0.1.1 is in active development. ### Source excerpt I'm excited to share something new I've been working on the past few months! ## State of the Configuration Cache - On the Road to Gradle 9 DevFeed: [State of the Configuration Cache - On the Road to Gradle 9]() Original publisher: [Read original article]() Author: Mikhail Lopatkin Published: 2025-03-14T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [configuration](), [build performance](), [Caching](), [Developer experience]() Tags: [build](), [caching](), [configuration](), [developer-experience](), [gradle](), [incremental](), [performance]() ### AI overview This article explains the state of Gradle's Configuration Cache ahead of Gradle 9.0. It describes how the feature reduces repeated configuration-phase work, improves build performance and developer experience, and is planned to become the preferred execution mode before being enabled by default in Gradle 10.0. ### Source excerpt Introduction As Gradle 9.0 approaches, we're sharing updates on the Configuration Cache--a key feature that significantly improves configuration time for large projects. In this major release, we plan to make the Configuration Cache the preferred execution mode, with the goal of enabling it by default in Gradle 10.0. The Configuration Cache is one of Gradle's most anticipated features; progress has been substantial. As Gradle Fellow Tony Robalik noted: "I'm excited about all the work Gradle has done to make the Configuration Cache stable and the preferred mechanism for running builds. At work, we've observed that enabling Configuration Cache globally will recover roughly 4 years of lost engineering time annually. The configuration cache also lays the foundation for Isolated Projects, which has been an eagerly awaited feature since Gradle first announced it several years ago!". Read this post to learn more about recent Configuration Cache performance and compatibility improvements, how to adopt it, and our plans for future releases. A Bit of History Development often happens in small increments--you write some code, run tests, fix failures, and repeat. In a build tool, this means executing the same tasks repeatedly. Gradle's execution model consists of three phases: Initialization - Discovers the project structure. Configuration - Builds the task graph. Execution - Runs tasks to perform the actual work. In an incremental workflow, where the same tasks are requested without changes to the build scripts, the configuration phase typically produces an identical task graph each time. Gradle excels at build caching, which caches the execution phase. This allows even massive projects and mono repositories to build in just a few seconds when no significant changes occur. However, generating the task graph for a complex project during the configuration phase can take a non-trivial amount of time. In some cases--like the project shown in the screenshot below--this overhead may eve ## When do you really need a monorepo? DevFeed: [When do you really need a monorepo?]() Original publisher: [Read original article]() Author: Emma Adler Published: 2025-02-26T00:00:00Z Content type: tutorial Language: en Sources: [Mintlify Blog]() Topics: [monorepo](), [Software Engineering](), [Dependency management](), [build performance](), [CI/CD]() Tags: [best-practices](), [build-performance](), [ci-cd](), [code](), [collaboration](), [dependency-management](), [documentation](), [monorepo](), [software-engineering]() ### AI overview This guide helps software engineering teams choose between monorepo and multi-repo strategies. It compares code sharing, dependency management, build performance, CI/CD pipelines, documentation consistency, collaboration, and access control, while describing how large organizations use monorepos. ### Source excerpt Software engineering teams often face an important decision: "Should all projects live in one repository or be split across multiple repositories?" This decision impacts build times, CI/CD pipelines, dependency management, and even documentation accuracy. ## Wise Tech Stack (2025 update) DevFeed: [Wise Tech Stack (2025 update)]() Original publisher: [Read original article]() Author: Milon James Published: 2025-02-12T13:34:08Z Content type: article Language: en Sources: [Wise Engineering - Medium]() Topics: [Development](), [Mobile](), [Web](), [Tuist](), [Storybook](), [Testing](), [build performance]() Tags: [build-times](), [caching](), [data](), [engineering](), [mobile](), [next-js](), [platform](), [storybook](), [swift](), [swift-package-manager](), [tech](), [tech-stack](), [testing](), [tuist](), [update](), [web](), [xcode](), [xcodegen]() ### AI overview Wise's 2025 technology update describes its web, iOS, and Android engineering stack, including Next.js-based web applications, Storybook visual testing, migration from Xcodegen to Tuist, adoption of Swift Package Manager, and Android development across a large Gradle repository. ### Source excerpt Wise Engineering As of the financial year 2025, Wise supports 15.6 million active customers, moving approximately GBP 36 billion across borders each quarter. Approximately 65% of our transfers arrive instantly, and our Wise Platform facilitates payments for banks, financial institutions and enterprises globally. This success is driven by our technology-first approach, robust architecture, and dedicated engineering teams. Photo by Randy Fath on UnsplashHow we work at Wise Wise has more than 850 engineers working across key global locations, organised into independent squads and tribes. These teams are empowered to innovate and make decisions independently, fostering transparency, trust, and collaboration. This article follows our Tech Stack 2022 to cover the most recent improvements in Wise's tech stack that enable us to achieve our mission of money without borders -- instant, convenient, transparent and eventually free. Moving money with WiseOur web and mobile applications Our web applications are built using CRAB (a Wise-specific abstraction on top of the popular Next.js framework) and comprises of 40 distinct apps, each handling specific product functions making deployments safer and more manageable. One of the biggest changes has been in our testing methodology. We've adopted Storybook for visualising individual React components during development. Storybook pairs really well with Chromatic which captures snapshots after each change and can highlight the visual differences in the component. These snapshots are very effective for catching visual regressions during code changes which helps us prevent bugs from reaching our customers. Wise mobile app: faster, smarter, and more efficient Our iOS engineers have upgraded our infrastructure by migrating 250+ Xcode modules from Xcodegen to Tuist and switching from Cocoapods to Swift Package Manager (SPM), unlocking improvements in caching for builds. The team also improved flexibility, reducing zero-change build times from 2 ## Tailwind CSS v4.0 Beta 1 DevFeed: [Tailwind CSS v4.0 Beta 1]() Original publisher: [Read original article]() Published: 2024-11-21T18:30:00Z Content type: release Language: en Sources: [Tailwind CSS Blog]() Topics: [Tailwind CSS](), [CSS](), [build performance](), [modern web development](), [Tooling]() Tags: [compatibility](), [developer-experience](), [framework](), [performance](), [release](), [tailwind](), [tailwind-css](), [tooling]() ### AI overview Tailwind CSS v4.0 Beta 1 is the first public beta release after an extended alpha period. The new engine is designed for performance and the modern web, with faster full and incremental builds, a unified toolchain, CSS-first configuration, and support for modern CSS features. ### Source excerpt After a long alpha period, we're excited to release the first public beta of Tailwind CSS v4.0. [Next page]()