# lazy Published articles for lazy. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What You Need to Know About Lazy Evaluation in Nix DevFeed: [What You Need to Know About Lazy Evaluation in Nix]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2024-07-15T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [Functional programming](), [Programming]() Tags: [article](), [functional-programming](), [lazy](), [programming]() ### AI overview This article explains lazy evaluation in the Nix language, including when expressions are evaluated, how errors can be deferred until a value is referenced, and how thunks model this behavior. It also introduces context for understanding Nix overlays and dependency overrides. ### Source excerpt If you have no prior experience with functional programming, don't miss this article which explains the most important intricacies of lazy evaluation! ## Lazy property delegate DevFeed: [Lazy property delegate]() Original publisher: [Read original article]() Published: 2023-03-27T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Optimization](), [performance-optimization](), [properties]() Tags: [kotlin](), [lazy](), [performance](), [property](), [regex](), [workshop-learning-programming]() ### AI overview This tutorial explains Kotlin's lazy property delegate, which postpones read-only value initialization until first use. It presents use cases involving expensive object construction, application startup, testing, regular-expression compilation, and computed properties. ### Source excerpt What is lazy delegate, and what are its real-life use cases. ## Tony's rules for Gradle plugin authors DevFeed: [Tony's rules for Gradle plugin authors]() Original publisher: [Read original article]() Author: Tony Robalik Published: 2022-04-25T01:30:01Z Content type: tutorial Language: en Sources: [DEV Community: Tony Robalik]() Topics: [Gradle](), [configuration](), [ordering](), [debug]() Tags: [api](), [coding](), [community](), [configuration](), [container](), [context](), [debug](), [dependencies](), [deprecated](), [development](), [engineering](), [gradle](), [gradle-plugin](), [inclusive](), [lazy](), [plugin](), [releases](), [rules](), [software](), [types]() ### AI overview An advisory article for Gradle plugin authors that presents practical rules for separating configuration and execution, using lazy configuration and callbacks, avoiding cross-project configuration and internal APIs, and designing stable public APIs. ### Source excerpt The Gradle API surface is huge. It is also littered with unspoken rules whose enforcement mechanism is inscrutable runtime failures. I want to say "we can do better," but really, we can't. The best we can do at present is mitigate by internalizing the following rules. A rule by any other name I call these "rules," but in many cases they can be only guidelines. Sometimes we have to break a rule because there really is no other way to achieve our goals. Nevertheless, the following rules were all learned the hard way, and should only be violated consciously. The rules An important bit of context for the following is that a Gradle build is divided into two1 primary phases: configuration and execution. Most of the rules are about what it is permissible to do in one phase or the other. Each phase carries with it different restrictions. Don't do expensive computations in the configuration phase It slows down the build. Such computations should be encapsulated in a task action. Avoid the create method on Gradle's container types Use register instead. Avoid the all callback on Gradle's container types Use configureEach instead. Don't assume your plugin is applied after another Instead, use pluginManager.withPlugin(). Avoid making any ordering assumptions of any kind Lazy configuration, callbacks, and provider chains are the name of the game. Don't access a Project instance inside a task action It breaks the configuration cache, and will eventually be deprecated. Don't access another project's Project instance This is called cross-project configuration and is extremely fragile. It creates implicit, nearly un-modelable dependencies between projects and can only lead to grief. Instead, share artifacts across projects by declaring dependencies. It also breaks the experimental project isolation feature, but that won't be truly relevant for a while. Avoid afterEvaluate It introduces subtle ordering issues which can be very challenging to debug. What you're looking for is probably ## Effective Kotlin Item 54: Prefer Sequences for big collections with more than one processing step DevFeed: [Effective Kotlin Item 54: Prefer Sequences for big collections with more than one processing step]() Original publisher: [Read original article]() Published: 2021-09-20T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Sequences](), [Collections](), [.NET]() Tags: [collections](), [kotlin](), [lazy](), [order-of-operations](), [sequences](), [workshop-learning-programming]() ### AI overview This article explains the difference between Kotlin collection and sequence processing. Sequences are lazy: intermediate operations build a processing chain, and calculations occur during terminal operations. The article discusses their element-by-element ordering, reduced processing work, support for infinite sequences, and avoidance of intermediate collections. ### Source excerpt What the difference between list and sequence processing is, and when each should be preferred. ## 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 ## el-get 2.1 DevFeed: [el-get 2.1]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2011-05-26T08:00:00Z Content type: release Language: en Sources: [Dimitri Fontaine]() Topics: [Emacs](), [version]() Tags: [custom](), [emacs](), [features](), [functions](), [lazy](), [release](), [repositories]() ### AI overview The el-get 2.1 release is described as stable and ready for daily use. It adds or includes autoload support, byte-compiling in an external clean Emacs instance, custom support, lazy initialization, and support for multiple repositories. ### Source excerpt Current el-get status is stable, ready for daily use and packed with extra features that make life easier. There are some more things we could do, as always, but they will be about smoothing things further. Latest released version el-get version 2.1 is available, with a boatload of features, including autoloads support, byte-compiling in an external clean room Emacs instance, custom support, lazy initialisation support (defering all init functions to eval-after-load), and multi repositories ELPA support.