# performant Published articles for performant. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Fast and Hard Code DevFeed: [Fast and Hard Code]() Original publisher: [Read original article]() Author: Armin Ronacher Published: 2026-08-22T00:00:00Z Content type: opinion Language: en Sources: [Armin Ronacher]() Topics: [Rust](), [LLMs](), [Zig](), [Artificial Intelligence](), [Programming](), [WebAssembly](), [Cloudflare](), [Vercel](), [eBPF]() Tags: [ai](), [cloudflare](), [ebpf](), [llms](), [performant](), [programming](), [rust](), [thoughts](), [vercel](), [webassembly](), [zig]() ### AI overview An opinion article argues that LLM-assisted programming makes language choice less consequential, allowing developers to use unfamiliar or traditionally difficult languages. It focuses on growing interest in fast, small software built with Rust and Zig, while noting examples involving WebAssembly, Cloudflare, Vercel, and other demanding technologies. ### Source excerpt One of the memes on Twitter is that "programming is solved now." I'm not sure to what degree it is, but one thing is pretty clear: the act of familiarizing yourself with a language no longer matters and some of the friction that mattered for humans does not matter for agents. As a result, LLMs make language choice much less consequential than it used to be. If you don't like the choice, you can seemingly rewrite it in another language and you can make it pick a language that you, as a programmer, are entirely unfamiliar with. Which in turn means that people can, and do, choose based on the marketing of languages much more. As a long-term Rust programmer I found it quite fascinating to see people now ship Rust code who previously might not have chosen it. I attribute at least one part of this to two recent vibe shifts: there is a lot more talk about wanting fast software, and about LLMs being exceptional at optimizing code without regressing behavior. Folks like Mitchell Hashimoto, Charlie Marsh, Jarred Sumner, Daniel Lemire and quite a few others always carried a certain level of obsession with fast and performant software and they also all happen to be receptive to agents writing code. Maybe as a result, or unrelated others are now joining in. That's because with things like autoresearch you don't even necessarily need to know all the tricks: you just need to put an agent on it -- though knowledge greatly helps! If you look around, there are plenty of projects that want to be fast and small, and they increasingly pick "hard languages". And it's not just Rust that is benefiting. Even Zig -- despite the fact that the creators and parts of the core community are pretty negative on the whole AI thing -- is too. For instance Cloudflare's new Artifacts service uses a pure-Zig Git-protocol engine, compiled to a roughly 100 KB WebAssembly module and Vercel released fx, a Zig coding agent advertised to be small and fast. From what I can tell, all these projects are largely LLM ## 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 ## Simple Static Asset Versioning in Craft CMS DevFeed: [Simple Static Asset Versioning in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-05-05T20:58:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Caching](), [JavaScript](), [Web Development](), [Website]() Tags: [allows](), [asset](), [caching](), [cms](), [css](), [delivered](), [ensuring](), [frontend](), [insights](), [javascript](), [latest](), [performance](), [performant](), [static](), [versioning](), [website]() ### AI overview This tutorial explains static asset versioning in Craft CMS. It describes browser caching for CSS, JavaScript, and image assets, compares query-string and filename-based cache busting, and presents a simple approach to delivering updated assets while keeping the build system manageable. ### Source excerpt Static asset versioning allows you to have a performant website, while also ensuring the latest CSS and JavaScript are delivered ## Implementing Critical CSS on your website DevFeed: [Implementing Critical CSS on your website]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-02-28T21:34:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [modern web development](), [Web Development](), [Front end](), [inlining](), [render](), [Website]() Tags: [article](), [browser](), [critical](), [development](), [essential](), [frontend](), [how-to](), [implementing](), [inlining](), [insights](), [modern](), [modern-web-development](), [performant](), [render](), [shows](), [website]() ### AI overview This tutorial explains Critical CSS, a method for extracting the CSS needed for above-the-fold content and inlining it so the browser can render the page immediately. It presents the technique as part of building performant websites. ### Source excerpt Implementing Critical CSS is an essential part of modern website development, this article shows you how to do it ## ActiveObjects streaming API DevFeed: [ActiveObjects streaming API]() Original publisher: [Read original article]() Author: Alex Hennecke Published: 2011-09-30T03:28:25Z Content type: release Language: en Sources: [Atlassian Developer Blog]() Topics: [API]() Tags: [allows](), [api](), [greenhopper](), [jira](), [performant](), [plugins](), [reading](), [tables]() ### AI overview The article announces a new ActiveObjects API for performant reading of large tables. ### Source excerpt New API for ActiveObjects allows performant reading of large tables