# build performance Published articles for build performance. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## 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. ## Pure Virtual C++ 2026 Is a Wrap DevFeed: [Pure Virtual C++ 2026 Is a Wrap]() Original publisher: [Read original article]() Author: Marian Luparu Published: 2026-07-22T16:00:35Z Content type: news Language: en Sources: [C++ Team Blog]() Topics: [C++](), [Visual Studio 2026](), [build times]() Tags: [ai](), [announcement](), [build-performance](), [c-plus-plus](), [conference](), [interop](), [pure-virtual-c-plus-plus]() ### AI overview Pure Virtual C++ 2026 has concluded, and recordings of its featured and on-demand C++ conference sessions are available. Topics include C++/Rust interoperability, AI-assisted tooling, build times, C++20 modules, packages, MSVC, and profile-guided optimization. ### Source excerpt Pure Virtual C++ 2026 is a wrap. Every featured and on-demand session is now available on YouTube -- catch up on C++/Rust interop, AI-driven tooling, build performance, and more. The post Pure Virtual C++ 2026 Is a Wrap appeared first on C++ Team Blog. ## Faster C++ iterative builds with GitHub Copilot DevFeed: [Faster C++ iterative builds with GitHub Copilot]() Original publisher: [Read original article]() Author: David Li Published: 2026-07-17T14:22:57Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [build times](), [C++](), [AI Bots]() Tags: [agent](), [build-insights](), [build-optimization](), [build-performance](), [build-times](), [c-plus-plus](), [copilot](), [diagnostics](), [game-development](), [github](), [github-copilot](), [optimization](), [performance](), [tool](), [visual-studio](), [visual-studio-2026](), [windows](), [workflow]() ### AI overview GitHub Copilot build performance for Windows adds an iterative build tool that evaluates optimization changes against incremental builds as well as clean builds. ### Source excerpt Slow builds are a consistent theme of feedback from C++ developers. We built GitHub Copilot build performance for Windows so you can leverage Copilot to optimize your project's build times. This workflow will find optimizations that bring your build times down. At first, we only measured the impact of build optimizations on full clean builds. [...] The post Faster C++ iterative builds with GitHub Copilot appeared first on C++ Team Blog. ## Essential Tips for Gradle on Ephemeral CI Environments - Part 2 DevFeed: [Essential Tips for Gradle on Ephemeral CI Environments - Part 2]() Original publisher: [Read original article]() Author: Louis Jacomet Published: 2026-07-08T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Caching](), [benchmarking](), [Spring Boot](), [Docker](), [GitHub]() Tags: [benchmarking](), [build-performance](), [cache](), [docker](), [github](), [gradle](), [jdk](), [spring-boot]() ### AI overview Part 2 examines Gradle configuration-phase performance in ephemeral CI environments, focusing on dependency and script caching and the roles of the setup-gradle GitHub Action and Develocity Universal Cache. ### Source excerpt In Part 1, we explored foundational strategies for improving Gradle build performance in ephemeral CI environments, focusing on the Startup and Initialization phase. Now, in Part 2, we shift our focus to the Configuration phase: the work Gradle does after startup but before it executes any tasks. We'll benchmark dependency and script caching, then look at where the setup-gradle GitHub Action and Develocity's Universal Cache fit. Benchmarking Performance in Ephemeral CI The methodology is the same as in Part 1: each scenario builds a fresh Docker image of the Spring Boot Project with --no-cache, base images are pre-pulled, and every figure is the average of ten runs against one consistent baseline. Individual runs vary by a second or two, so read small differences as approximate rather than exact. These numbers are not intended as universal Gradle performance claims. They show the relative impact of configuration-phase optimizations for one small Spring Boot project, one Gradle version, one JDK image, and one local Docker environment. Larger builds, with more dependencies and more build logic, will generally see bigger gains from dependency and script caching than a small sample project does. NOTE: All measurements in this post are pinned to Gradle 9.5.1. If you repeat the experiment with a newer Gradle version, rebuild the prime image and update any version-specific cache paths accordingly. One difference from Part 1: for the Configuration phase, we prime the cache by building the complete Spring Boot Project, not the empty Prime Project. Caching configuration-phase work only means something when there are real dependencies and real build scripts to cache, so the prime image must reflect a realistic project. As in Part 1, that prime image is built once and only restored from, so the timed builds measure cache restore, not cache creation. Building the full project populates the following directories in the Gradle User Home: .gradle/ <-- Gradle User Home (default: ~/. ## 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 ## Metro 1.0.0 Is Stable as a Kotlin Multiplatform Compile-Time Dependency Injection Framework DevFeed: [Metro 1.0.0 Is Stable as a Kotlin Multiplatform Compile-Time Dependency Injection Framework]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-04-27T21:07:22Z Content type: release Language: en Sources: [Zac Sweers]() Topics: [Kotlin](), [Dependency injection](), [multiplatform](), [Compiler](), [Framework](), [gradle-plugin]() Tags: [build-performance](), [build-times](), [compilation](), [compiler](), [dependency-injection](), [experimental](), [gradle](), [gradle-plugin](), [incremental](), [kotlin](), [metro](), [multiplatform](), [open-source](), [perfetto](), [stable]() ### AI overview Metro 1.0.0 is now stable. The Kotlin multiplatform compile-time dependency injection framework uses a compiler plugin and provides API-stable runtime APIs, MetroX artifacts, and a Gradle plugin unless marked experimental. The article also describes build-performance improvements and compile-time validation features. ### Source excerpt New here? Metro is a multiplatform, compile-time dependency injection framework for Kotlin implemented as a compiler plugin. Metro 1.0.0 is out now and stable. This means that its runtime APIs (runtime, MetroX artifacts, Gradle plugin, etc.) are now API-stable unless annotated with an experimental annotation. This ## Elastic build machines now available in beta DevFeed: [Elastic build machines now available in beta]() Original publisher: [Read original article]() Author: Marcos Grappeggia Published: 2026-03-24T07:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [CI/CD]() Tags: [build-performance](), [performance](), [vercel]() ### AI overview Vercel has released elastic build machines in beta for paid plans. Teams can configure builds at team or project level, with projects assigned Standard, Enhanced, or Turbo machines according to workload needs. ### Source excerpt Elastic build machines are now available in beta for all paid plans, giving teams control over build performance without project-level micromanagement. You can configure elastic builds at the team or project level. Rather than a one-size-fits-all approach, Vercel evaluates each project individually and assigns the right machine for its actual needs. Smaller, simpler projects may benefit from cost-efficient Standard build machines while more complex workloads can automatically scale up to Enhanced or Turbo machines. This smart assignment prevents over-provisioning, with teams automatically getting optimal performance at the right cost for every project. Enable elastic builds in your team settings or project settings, or read the builds documentation. Read more ## 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 ## Vite 8 Beta: The Rolldown-powered Vite DevFeed: [Vite 8 Beta: The Rolldown-powered Vite]() Original publisher: [Read original article]() Author: The Vite Team Published: 2025-12-03T00:00:00Z Content type: release Language: en Sources: [Vite]() Topics: [build times](), [Web Development]() Tags: [build-performance](), [javascript](), [migration](), [performance](), [release](), [rust](), [toolchain]() ### AI overview Vite 8 beta replaces its esbuild-and-Rollup pipeline with the Rust-based Rolldown bundler. The release emphasizes faster production builds, more consistent development and production behavior, and an integrated Vite, Rolldown, and Oxc toolchain. ### Source excerpt Vite 8 Beta: The Rolldown-powered Vite December 3, 2025 TL;DR: The first beta of Vite 8, powered by Rolldown, is now available. Vite 8 ships significantly faster production builds and unlocks future improvement possibilities. You can try the new release by upgrading vite to version 8.0.0-beta.0 and reading the migration guide. ## Next.js 15.5 DevFeed: [Next.js 15.5]() Original publisher: [Read original article]() Author: Luke Sandberg Published: 2025-08-18T20:00:00Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [build times](), [Node.js](), [web applications]() Tags: [build-performance](), [next-js](), [node-js](), [release](), [typescript]() ### AI overview Next.js 15.5 adds Turbopack production builds in beta, stable Node.js middleware support, TypeScript enhancements, and deprecation warnings ahead of Next.js 16. ### Source excerpt Next.js 15.5 includes Turbopack builds in beta, stable Node.js middleware, TypeScript improvements, `next lint` deprecation, and deprecation warnings for Next.js 16. ## 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. ## 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! ## 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. ## Docusaurus 3.6 DevFeed: [Docusaurus 3.6]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2024-11-04T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [build performance](), [build times](), [Memory Leaks](), [Compiler](), [Rust]() Tags: [build-performance](), [build-times](), [bun](), [ci](), [memory-leak](), [npm](), [pnpm](), [release]() ### AI overview Docusaurus 3.6 introduces the opt-in Docusaurus Faster infrastructure project, using Rust-based tools to improve build performance and reduce memory consumption. Community benchmarks report production builds that are 2 to 4 times faster, alongside a fixed memory leak and smaller static HTML output. ### Source excerpt We are happy to announce Docusaurus 3.6. ## Next.js 15 DevFeed: [Next.js 15]() Original publisher: [Read original article]() Author: Rich Haines Published: 2024-10-21T17:00:00Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [Caching](), [React](), [build performance](), [Command-line interface](), [Server-side rendering]() Tags: [build](), [build-performance](), [caching](), [cli](), [eslint](), [next-js](), [performance](), [react](), [streaming]() ### AI overview Next.js 15 is presented as a stable, production-ready release focused on stability and updated rendering behavior. It adds React 19 support, experimental React Compiler support, changed caching defaults, stable Turbopack development support, new APIs, enhanced forms, self-hosting improvements, Server Actions security changes, ESLint 9 support, and improved development and build performance. ### Source excerpt Next.js 15 introduces React 19 support, caching improvements, a stable release for Turbopack in development, new APIs, and more. ## Nuxt 3.13 DevFeed: [Nuxt 3.13]() Original publisher: [Read original article]() Author: New Features Published: 2024-08-22T00:00:00Z Content type: release Language: en Sources: [The Nuxt Blog]() Topics: [Nuxt.js](), [Vue.js](), [Search engine optimization (SEO)](), [build performance]() Tags: [build-performance](), [dependencies](), [nuxt](), [release](), [seo](), [types](), [updates](), [vue]() ### AI overview Nuxt 3.13 ports selected Nuxt 4 features back into the current release, including route groups, server component island head manipulation, custom link prefetch triggers, and improved source maps for Vue files in server builds. ### Source excerpt Nuxt 3.13 is out - porting back some of the new features we're building for Nuxt 4! ## Stop Repeating Yourself 2: Using Test Fixtures with AGP DevFeed: [Stop Repeating Yourself 2: Using Test Fixtures with AGP]() Original publisher: [Read original article]() Author: Michael Evans Published: 2024-07-29T23:43:27Z Content type: tutorial Language: en Sources: [Gadget Habit]() Topics: [Android Gradle Plugin](), [Testing](), [Gradle](), [build performance](), [Mobile]() Tags: [android-development](), [android-gradle-plugin](), [build](), [build-performance](), [configuration](), [gradle](), [plugin](), [testing](), [tests]() ### AI overview This tutorial explains how Android Gradle Plugin 8.5.0 adds native support for reusable test fixtures in modularized Android projects. It covers defining shared test utilities such as mocks, fakes, and test data, then consuming them from other modules. ### Source excerpt Modern Android development often involves modularization to enhance build performance and maintainability. As you break down your app into multiple modules, sharing test utilities such as fixtures, mocks, or fakes between modules can become challenging. A few years ago I wrote about the concept of test fixtures, but at the time they weren't supported for Android modules. Thankfully, with Android Gradle Plugin (AGP) 8.5.0, Google introduced native support for test fixtures, streamlining this process significantly. What Are Test Fixtures? Test fixtures are reusable components such as test data, helper classes, or mocks that you can use to support your tests. Prior to AGP 8.5.0, sharing these utilities across modules often required workarounds like creating dedicated "test" modules or manually wiring dependencies. With AGP 8.5.0, the testFixtures feature makes it easier to declare and consume test fixtures directly from your modules. Setting Up Test Fixtures To enable test fixtures for a module, you need to include the testFixtures feature in your module's build.gradle.kts file. Here's how you can set it up: 1 2 3 4 5 6 7 8 9 android { // Enable test fixtures for the module testFixtures.enable = true } dependencies { // Declare dependencies for your test fixtures testFixturesImplementation("com.example:some-library:1.0.0") } The testFixtures source set is automatically created under the src directory: 1 2 3 4 5 6 7 8 9 module-name/ src/ main/ java/ testFixtures/ java/ kotlin/ test/ java/ You can now place reusable test utilities, such as mock data generators or fake implementations, inside the testFixtures directory. Consuming Test Fixtures Modules can consume test fixtures by declaring a dependency on the testFixtures configuration of another module. For example, if module-b needs to use the test fixtures from module-a, add the following dependency: 1 2 3 dependencies { testImplementation(testFixtures(project(":module-a"))) } Once this dependency is added, the test co ## Journey to K2: using the New Compiler in Apollo Kotlin DevFeed: [Journey to K2: using the New Compiler in Apollo Kotlin]() Original publisher: [Read original article]() Author: Benoit Lubek Published: 2024-06-19T08:26:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [Kotlin](), [Compiler](), [migration](), [build performance]() Tags: [build-performance](), [compilation](), [compiler](), [compose](), [gradle](), [kotlin](), [migration](), [mobile]() ### AI overview Apollo Kotlin migrated to K2, the rewritten Kotlin compiler frontend released with Kotlin 2. The article describes the migration process, including compilation errors, language differences, compiler bugs, and changes to the Compose compiler and Gradle configuration. ### Source excerpt Apollo Kotlin is now built with K2, the new compiler that has recently been released with Kotlin 2. Here are a few details on the migration process. What is K2? K2 is a complete rewrite of the Kotlin compiler frontend, " the part of the compiler that parses your code and performs the semantic analysis, data flow analysis, call resolution, and type inference " (source). The result is a faster, more robust and reliable compiler that should also be easier to evolve in the future. ## The Astro Content Layer DevFeed: [The Astro Content Layer]() Original publisher: [Read original article]() Author: Fred Schott Published: 2024-06-12T00:00:00Z Content type: article Language: en Sources: [The Astro Blog]() Topics: [Astro](), [Content Management System](), [MDX](), [Markdown](), [API](), [libSQL](), [SQLite](), [SQL](), [Serverless](), [Server-side rendering](), [TypeScript](), [build performance]() Tags: [api](), [astro](), [build-performance](), [cache](), [content](), [libsql](), [management](), [markdown](), [series](), [serverless](), [sql](), [sqlite](), [ssr](), [typescript]() ### AI overview Part 2 of The Future of Astro series presents a planned Content Layer for working with local and remote content sources. It proposes extending Content Collections with a more capable content engine backed by LibSQL (SQLite), enabling larger content sets, file-based caching across builds, faster development and build performance, and more advanced SQL-powered querying. ### Source excerpt Part two of our series on The Future of Astro, covering our plans for the next evolution of content management in Astro. ## Reduce Kotlin Multiplatform iOS Build Times by Building Only the Needed Architecture DevFeed: [Reduce Kotlin Multiplatform iOS Build Times by Building Only the Needed Architecture]() Original publisher: [Read original article]() Published: 2024-04-19T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [build performance](), [iOS](), [Gradle]() Tags: [architectures](), [build-performance](), [gradle](), [ios](), [kotlin](), [kotlin-multiplatform]() ### AI overview This article explains that Kotlin Multiplatform iOS builds can become unnecessarily slow when they compile for Intel simulator, Arm simulator, and physical-device architectures at once. It recommends building only the architecture needed for local development, CI tests, or app publishing. ### Source excerpt Slow Kotlin Multiplatform iOS build times? Many teams are building more architectures than needed or intended. Ensure you are not wasting build time ## 2023 Lunar Year in Review DevFeed: [2023 Lunar Year in Review]() Original publisher: [Read original article]() Author: Oleg Nenashev Published: 2024-02-12T05:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Kotlin](), [releases](), [Caching](), [build performance](), [Scalability](), [Android Studio](), [IntelliJ IDEA](), [Groovy]() Tags: [android-studio](), [build-performance](), [caching](), [gradle](), [groovy](), [ide](), [intellij-idea](), [kotlin](), [releases](), [scalability](), [year-in-review]() ### AI overview This article reviews Gradle's 2023 updates, including the Gradle 8 baseline, Kotlin DSL becoming the recommended default for new projects, configuration caching, build performance and scalability improvements, community initiatives, the renaming of Gradle Enterprise to Develocity, and plans for Declarative Gradle and Gradle 9. ### Source excerpt Hi all! On behalf of the Gradle community, we wish you a Happy New Lunar Year! 2023 was a great year for Gradle Build Tool, with many new features and initiatives being released. Let's recap the key updates: Gradle 8 baseline with 7 feature packed releases Kotlin DSL became the new default for Gradle Configuration Caching, Build Speed and Scalability Improvements Our First Google Summer of Code and Major League Hacking participation Gradle Enterprise renaming to Develocity, and Gradle Build Scan enhancements What's next, Declarative Gradle and the road towards Gradle 9 Gradle 8 In February 2023, the Gradle team announced Gradle 8.0 - a new release that upgraded Kotlin DSL to v1.8 and greatly improved its compilation speed. Gradle 8.0 expanded integration with Java tools like CodeNarc, PMD, and Foojay Disco API for toolchain management. This major release had more than 40 code contributors from the Gradle community. Thanks, everyone! See this blog post for the full list of the introduced features and the migration guidelines. After the 8.0 release, we had 6 more major releases with many more features. Beyond the key updates listed below, you can find more in the changelogs and our newsletter. Kotlin DSL is the New Default In April 2023, Kotlin DSL became the default recommended option for new Gradle projects. Kotlin DSL for Gradle uses the Kotlin language to enable full IDE assistance for build authoring in IntelliJ IDEA and Android Studio. This includes auto-completion, smart content assist, quick access to documentation, navigation to source, and context-aware refactoring. With Kotlin DSL, you can edit your build logic with the same editing experience you are used to when working with your production and test code. Groovy DSL remains fully supported, and there are no plans for deprecation. Learn More about Kotlin DSL in Gradle. Culminating efforts around Kotlin DSL in Gradle and its massive adoption in 2023, Gradle joined the Kotlin Foundation as a silver member. S [Next page]()