# lazy loading A computing technique that defers loading non-critical resources or CUDA modules until they are needed, reducing initial load or program initialization time. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How ORM N+1 Queries Create Hidden Request Latency DevFeed: [How ORM N+1 Queries Create Hidden Request Latency]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-08-02T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Object-relational mapping](), [Latency](), [Monitoring](), [lazy loading](), [Database](), [connection pool]() Tags: [connection-pool](), [database](), [database-performance](), [hibernate](), [latency](), [lazy-loading](), [monitoring](), [n-plus-one](), [observability](), [orm](), [query](), [request]() ### AI overview This article explains how ORM lazy loading can turn a loop over orders into an N+1 query pattern. Individual queries may remain fast and avoid slow-query alerts, while the accumulated network round trips increase request latency and hold connection-pool resources. It recommends monitoring queries per request and asserting query counts in tests. ### Source excerpt N+1 queries hide from monitoring because no individual query is slow. Four hundred queries at 0.4ms each never appear in the slow query log, never move p99 query latency, and still cost the request 300ms because the expense is the round trip rather than the execution. The metric that catches it is queries per request, and the only durable fix is asserting on that count in tests, since the code that causes it looks like a field access rather than I/O. ## How To Use Standard HTML Video & Audio Lazy-Loading on the Web Today DevFeed: [How To Use Standard HTML Video & Audio Lazy-Loading on the Web Today]() Original publisher: [Read original article]() Author: Scott Jehl Published: 2026-04-07T14:30:00Z Content type: tutorial Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [HTML](), [lazy loading](), [web-standards](), [browsers](), [Web Development]() Tags: [audio](), [best-practices](), [browsers](), [gotchas](), [how-to](), [html](), [lazy-loading](), [video]() ### AI overview This tutorial explains how to use standard HTML video and audio lazy loading on websites. It covers recommended practices and common implementation pitfalls, noting that the feature is gaining support in major browsers. ### Source excerpt HTML video and audio lazy loading is now a web standard and quickly gaining support in all major browsers. Given Squarespace's role in proposing and implementing it, we're very excited to see how developers use it on the web. Let's cover some best practices for using video and audio lazy loading in any website, as well as some gotchas to avoid. ## Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers DevFeed: [Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers]() Original publisher: [Read original article]() Author: Scott Jehl Published: 2026-03-30T21:00:00Z Content type: article Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [web-standards](), [lazy loading](), [HTML](), [Web platform](), [WebKit](), [Chromium](), [Google Chrome](), [Firefox]() Tags: [browsers](), [chrome](), [chromium](), [firefox](), [html](), [lazy-loading](), [standards](), [web-standards]() ### AI overview Squarespace engineers describe how they helped add lazy loading for HTML video and audio to the HTML Standard. They contributed proposed implementations for Firefox and WebKit, worked with Chromium developers on a Google Chrome implementation, and added automated testing. ### Source excerpt At Squarespace, many of our core products are built on web standards, and our engineers are constantly pushing the boundaries of the web's capabilities. Occasionally, those boundaries reveal a limitation: an opportunity for the web's native capabilities to grow. This post is the story of how we found such an opportunity to work with the standards community to improve the web in a way that we - and everyone who uses it - can benefit. ## Why I migrated to the Fish Shell DevFeed: [Why I migrated to the Fish Shell]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2020-12-07T00:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [friendly interactive shell](), [Shell](), [Zsh](), [Bash](), [dotfiles](), [Command-line interface](), [Environment Variables](), [lazy loading](), [Scripting]() Tags: [aliases](), [bash](), [environment-variables](), [lazy-loading](), [plugins](), [porting](), [prompt](), [scripting](), [shell](), [zsh]() ### AI overview The author explains migrating dotfiles from Zsh to Fish, emphasizing Fish's startup performance, universal variables, lazy loading, and built-in features such as syntax highlighting, autosuggestions, and man-page completions. The article also notes differences from POSIX shells and describes the author's plugin setup. ### Source excerpt Back in June, I started porting my dotfiles from ZSH to Fish. Here's why. ## Lazy Loading with the Element API & VueJS DevFeed: [Lazy Loading with the Element API & VueJS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-12-17T17:45:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [lazy loading](), [Content Management System](), [vuejs](), [API](), [Front end]() Tags: [api](), [cms](), [cms-s](), [content](), [craft](), [display](), [element](), [frontend](), [here-s](), [insights](), [lazy](), [lazy-loading](), [load](), [vuejs]() ### AI overview A tutorial on using Craft CMS's Element API with VueJS to lazy-load additional blog entries and display them on a frontend. It explains how to create an API endpoint that returns paginated blog content, including titles, URLs, summaries, images, categories, and tags. ### Source excerpt Here's how to use Craft CMS's Element API to lazy load content and display it via VueJS on the frontend ## WPF Explorer TreeView with SelectedPath binding DevFeed: [WPF Explorer TreeView with SelectedPath binding]() Original publisher: [Read original article]() Author: Andrew Khmylov Published: 2010-11-18T00:00:00Z Content type: tutorial Language: en Sources: [Despite the odds]() Topics: [WPF](), [Filesystems](), [lazy loading]() Tags: [build](), [file](), [lazy-loading]() ### AI overview This tutorial describes a custom WPF TreeView control for browsing file systems and exposing a SelectedPath property for two-way binding. It uses lazy loading to populate drives and subfolders, and synchronizes the TreeView selection with the selected path. ### Source excerpt While working on one of my projects, I had to implement a control for displaying file system. I found pretty good articles over the web ("A Simple WPF Explorer Tree" by Sacha Barber and some replies to it), but they were all about displaying folders. It was pretty easy to track currently selected folder, but there were some issues with its dynamic changes. So I decided to build my own control from scratch that will have some property like SelectedPath that will allow you to use TwoWay bindings to get and set selected folder at the tree. When user selects a node from the TreeView, text in the address bar is updated. When user enters address and clicks Update, TreeView selection gets updated. I have started with a simple CustomControl and inherited it from WPF TreeView: public class ExplorerTreeView: TreeView { public const string SelectedPathPropertyName = "SelectedPath"; public static readonly DependencyProperty SelectedPathProperty = DependencyProperty.Register( SelectedPathPropertyName, typeof (String), typeof (ExplorerTreeView)); public String SelectedPath { get { return (String) GetValue(SelectedPathProperty); } set { SetValue(SelectedPathProperty, value); } } } We will use some lazy-loading techniques to fill our TreeView with data. When control is loaded, it will display only drives on the user machine. Let's write a method for creating initial drive nodes: public void InitExplorer() { Items.Clear(); foreach (var drive in DriveInfo.GetDrives()) { Items.Add(GenerateDriveNode(drive)); } } private static TreeViewItem GenerateDriveNode(DriveInfo drive) { var item = new TreeViewItem { Tag = drive, Header = drive.ToString() }; item.Items.Add("*"); return item; } GenerateDriveNode method takes DriveInfo argument and builds TreeViewItem for it. Note that we are adding a dummy child node (the one with 'the star' header text). If we don't do this, then the user will not see a small button for expanding/collapsing for generated tree view item (it may look like '+' charac