# syntax Published articles for syntax. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Babel in Khan Academy's i18n Toolchain DevFeed: [Babel in Khan Academy's i18n Toolchain]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-06-22T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Babel](), [Internationalization (i18n)](), [toolchain](), [es6](), [JavaScript](), [Parser](), [Universal Syntax Tree.](), [Open Source]() Tags: [api](), [architecture](), [babel](), [build](), [build-system](), [code](), [engineering](), [es6](), [eslint](), [frontend](), [javascript](), [news](), [plugin](), [source](), [structure](), [syntax](), [tests](), [toolchain](), [types](), [web-frontend](), [workflow]() ### AI overview Khan Academy describes switching its ES6 and JSX frontend compilation from jstransform to Babel. The article explains a custom Babel plugin for preserving the project's internationalization behavior and discusses matching generated output, line numbers, whitespace, and the existing build chain. ### Source excerpt By Kevin Barabash We've been using ES6 (along with JSX) for sometime at Khan Academy. Right now, we're ... Read more ## Kotlin 2.4.20 Collection Checks and Experimental Context-Sensitive Resolution DevFeed: [Kotlin 2.4.20 Collection Checks and Experimental Context-Sensitive Resolution]() Original publisher: [Read original article]() Author: Andrii Dubovyk Published: 2026-09-14T06:32:51Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Kotlin](), [Compiler](), [Code]() Tags: [android](), [android-development](), [collections](), [compiler](), [experimental](), [features](), [kotlin](), [list](), [mobile-app-development](), [syntax](), [technology]() ### AI overview The article explains two Kotlin features: allDistinctBy and allEqualBy in Kotlin 2.4.20 for checking collection values, and experimental context-sensitive resolution introduced in Kotlin 2.2 to reduce repetition when the expected type is known. ### Source excerpt Kotlin 2.4.20 gives your collections opinions, and 2.2's compiler finally learns to read the room Some Kotlin features get a lot of attention when they arrive. Others are much less noticeable, but still make everyday code a little easier to write. Two examples of the latter are allDistinctBy/ allEqualBy in Kotlin 2.4.20 and context-sensitive resolution, which was introduced experimentally in Kotlin 2.2. allDistinctBy/ allEqualBy: A Simpler Way to Check Collections For years, checking whether all values in a collection were unique often looked something like this: val users = listOf( User(name = "A", age = 20), User(name = "B", age = 25), User(name = "C", age = 30) ) users.map { it.age }.distinct().size == users.size // true It works, but it creates another list, removes duplicates, counts the result, and then compares the sizes just to get a Boolean answer. Kotlin 2.4.20 adds a more direct way to express the same check: users.allDistinctBy { it.age } // true users.allEqualBy { it.age } // false allDistinctBy returns false as soon as it finds a duplicate, so it doesn't need to process the entire collection or create a separate Set. allEqualBy does the opposite: it checks whether all elements produce the same value when passed through the selector. Both functions work with Iterable, Sequence, and arrays. They use structural equality. For floating-point values, they follow Double.equals semantics, so NaN is considered equal to NaN, while -0.0 is different from 0.0. They're still @ExperimentalStdlibApi, so you'll need to opt in before using them in production code. The underlying allDistinct() and allEqual() requests have also been around in YouTrack for quite a while, which makes their appearance in the standard library feel long overdue. Context-Sensitive Resolution: Less Repetition in when The second feature is more about syntax. When the compiler already knows the type you're working with, you can sometimes leave out the type qualifier. Before: enum class Problem { ## Rust Function Overloading - Call for Experimentation DevFeed: [Rust Function Overloading - Call for Experimentation]() Original publisher: [Read original article]() Author: teor Published: 2026-08-19T00:00:00Z Content type: release Language: en Sources: [Inside Rust Blog]() Topics: [Rust](), [C++](), [Compiler](), [interoperability]() Tags: [c-plus-plus](), [compiler](), [interoperability](), [languages](), [rust](), [syntax]() ### AI overview The Rust Project is experimenting with function and method overloading for FFI bindings through the incomplete nightly "splat" compiler feature. The experiment aims to assess implementation complexity and improve interoperability with C++, while its design may change or be removed. ### Source excerpt In partnership with the Rust Foundation's Rust-C++ Interop Initiative, the Rust Project has been experimenting with function overloading for FFI bindings. This experiment is now at a stage where compiler and interop tool developers can start exploring function overloading. Stable Rust already supports a form of overloading using tuples and traits, but calling these overloaded functions looks strange, because the overloaded arguments have to be passed as a single tuple argument, like this: hypot((2.0, 3.0, 6.0)). Stable Rust also allows overloading of built-in operators with user-defined types, via traits like Add (the + operator) and Neg (the - value negation operator). We are running an unstable nightly Rust language experiment to answer questions like: How much overloading can we do with Rust's existing trait system? Could this help us call C++ from Rust ergonomically? In the tradition of yeet (to avoid bikeshedding), we are using basic syntax in the first stage of the experiment: the #[rustc_splat] attribute. Alternative syntaxes can be considered later, if the experiment generates useful outcomes. Experimental Function Overloading Rust nightly builds from 2026-07-31 onwards have experimental support for more ergonomic function and method overloading, using the incomplete "splat" compiler feature; if you're a compiler or interop tool developer, we encourage you to experiment with it! This experiment lets overloaded functions be called with separate arguments, like this: hypot(2.0, 3.0, 6.0). No double parentheses required! But type inference and type checking still happen as they would in a stable Rust overload. We are experimenting with splat to get a feel for the complexity of the implementation, and to see if it solves some language interoperability use cases. Like most Rust language experiments, this nightly feature has no RFC, and can change or be removed at any time. Experiment Design We expect the feature to change significantly in future, or to be replace ## How to Stop or Skip Cypress Test Commands DevFeed: [How to Stop or Skip Cypress Test Commands]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-08-07T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Mocha](), [test](), [Code]() Tags: [callback](), [command](), [commands](), [condition](), [cypress](), [object](), [products](), [skip](), [syntax](), [test](), [testing](), [tests]() ### AI overview This tutorial explains three ways to stop or skip Cypress test execution: using Cypress.stop, skipping the current Mocha test, and skipping the remaining commands in the Cypress command queue. It describes the trade-offs of each approach, including whether later tests run and whether completed commands remain visible. ### Source excerpt Let's say you have a long-ish Cypress test and you know a place where it might fail. You want to stop / skip the test commands. ## YAML for DevOps Beginners, Syntax, Rules and Common Mistakes DevFeed: [YAML for DevOps Beginners, Syntax, Rules and Common Mistakes]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-06T17:16:19Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [YAML](), [configuration](), [DevOps](), [Ansible](), [ci](), [Kubernetes]() Tags: [ansible](), [block-scalars](), [ci-cd](), [cloud](), [configuration](), [devops](), [errors](), [guide](), [how-to](), [json](), [kubernetes](), [kubernetes-yaml-manifests](), [linter](), [mistakes](), [multi-document-yaml](), [structure](), [syntax](), [validation](), [yaml](), [yaml-anchors-and-aliases](), [yaml-common-mistakes](), [yaml-for-devops](), [yaml-indentation-rules](), [yaml-norway-problem](), [yaml-syntax-rules](), [yaml-vs-json](), [yamllint-validation]() ### AI overview A tutorial explaining YAML syntax, implicit typing, indentation rules, block scalars, anchors, aliases, and merge keys. It emphasizes that YAML can silently reinterpret unquoted values and recommends linting and schema validation in CI pipelines. ### Source excerpt YAML tries to guess what you meant, and that is the entire problem. Once you know which values it silently reinterprets and why, the manifests that mysteriously break stop being mysterious. ## Rich Text And Code Editing: RichTextArea And A Syntax-Highlighting CodeEditor DevFeed: [Rich Text And Code Editing: RichTextArea And A Syntax-Highlighting CodeEditor]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-28T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Syntax Highlighting](), [Code](), [cross-platform](), [Web](), [JavaScript](), [Kotlin](), [Python](), [CSS](), [JSON](), [XML]() Tags: [code](), [code-completion](), [cross-platform](), [css](), [javascript](), [kotlin](), [python](), [syntax](), [web](), [xml]() ### AI overview The article describes RichTextArea and CodeEditor, two Codename One visual editors built on a shared semantic abstraction. A bundled cross-platform web-view engine is the default backend, while ports can provide optional native peers. The CodeEditor supports syntax highlighting for eight languages, themes, automatic bracket and quote closing, and asynchronous code completion. ### Source excerpt RichTextArea and a syntax-highlighting CodeEditor, both built on a shared editor abstraction with a cross-platform web-view engine and an optional native peer. ## The Four Kotlin Versions in a Gradle Project DevFeed: [The Four Kotlin Versions in a Gradle Project]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2026-06-12T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Kotlin](), [Compiler](), [Code]() Tags: [compiler](), [gradle](), [gradle-plugin](), [kotlin](), [kotlin-compiler](), [syntax]() ### AI overview This article explains the four Kotlin versions that can matter in a Gradle project: the Kotlin compiler version selected through the Kotlin Gradle Plugin, the language version targeted for project code, the Kotlin compiler bundled with Gradle for build logic, and the language version Gradle pins for that build logic. ### Source excerpt Do you know what version of Kotlin your Gradle build is using? There are four Kotlin versions you need to know about in a project built with Gradle. They're easy to mix up, and mixing them up can lead to some confusion (and the occasional compiler error). The trick is that there are really only two compilers in play, and each one carries its own language-version dial. Two compilers, two dials, four numbers. Let's take them one at a time. This post was updated on June 16, 2026. 1. The Kotlin that compiles your code This is the version most people look for. If your application or library code is written in Kotlin and gets compiled by the Kotlin Gradle Plugin, you pick its version in your build: // build.gradle.kts plugins { kotlin("jvm") version "1.9.25" } Change the KGP version, and you change the Kotlin compiler used to compile your project. This is the version you control directly. 2. The Kotlin language version for your code Picking the KGP version chooses which compiler runs over your code. But that compiler has a second dial: the language version, which decides what Kotlin syntax it will accept. You set it through KGP: // build.gradle.kts kotlin { compilerOptions { languageVersion = KotlinVersion.KOTLIN_1_8 } } By default it matches the language version associated with your KGP version, so most projects never touch it. You can pin it lower, for example to keep a library compilable by projects still on an older Kotlin. #1 is the compiler; this is the language level you ask that compiler to target. 3. The Kotlin embedded in Gradle (that compiles your build logic) Now the other compiler. Gradle ships its own Kotlin compiler and standard library inside the distribution. It's the compiler that builds your Kotlin DSL scripts and Gradle-managed build logic, and its standard library is available on the classpath used by build scripts and plugins. You never declare this one. It comes bundled with whatever Gradle version you use. In Gradle 9.6.0: # gradle/wrapper/gradle-w ## Kotlin 2.4 Brings Swift-Style Collection Syntax \[\] DevFeed: [Kotlin 2.4 Brings Swift-Style Collection Syntax \[\]]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-06-04T16:32:23Z Content type: article Language: en Sources: [Stories by Nav Singh 🇨🇦 on Medium]() Topics: [Kotlin](), [Boilerplate](), [Code](), [Compiler]() Tags: [build](), [collection](), [compiler](), [experimental](), [kotlin](), [kotlin-2](), [kotlin-standard-library](), [new-features](), [syntax]() ### AI overview This article explains Kotlin 2.4's experimental collection literals, which allow collections to be initialized with bracket syntax instead of functions such as listOf() or mutableListOf(). It also covers enabling the feature with the compiler option and discusses explicit declarations and type inference. ### Source excerpt Image generated using Perplexity In Kotlin 2.4, collection literals are introduced, making collection initialization more concise and readable. To define collections, we no longer need to use functions like listOf() or mutableListOf(). This reduces boilerplate and makes intent clearer at a glance, especially when working with simple, static data. It's currently an experimental feature. We need to opt in, and the syntax or behavior may evolve in future releases. Add the Xcollection-literals compiler option to the build file kotlin { jvmToolchain(21) compilerOptions { freeCompilerArgs.add("-Xcollection-literals") } }Code samples Bracket syntax [] + explicit declaration // Mutable list with explicit type declaration // val plFNames: MutableList = mutableListOf("Joe", "Alice") // Mutable list with brackets syntax val plFNames: MutableList = ["Joe", "Alice"] println(plFNames) // ["Joe", "Alice" ] Bracket syntax [] + type inference As per docs:Compiler defaults to List if it lacks sufficient information to infer the collection type.But it seems like Array as we can see in the screenshot 📸 👇 val plFNames = ["Joe", "Alice"] println(plFNames) // ["Joe", "Alice" ]Screenshot type inference -- typeReferences What's new in Kotlin 2.4.0 | Kotlin Kotlin 2.4 Brings Swift-Style Collection Syntax [] was originally published in ProAndroidDev on Medium, where people are continuing the conversation by highlighting and responding to this story. ## A guide to Transformer architecture in modern language models DevFeed: [A guide to Transformer architecture in modern language models]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-05-14T04:15:11Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Transformer architecture](), [LLMs](), [Transformer]() Tags: [architecture-pattern](), [better](), [deep-dive](), [layer](), [llms](), [model](), [parallel](), [performance](), [semantics](), [sequence](), [syntax](), [tokens](), [transformer-architecture](), [transformers]() ### AI overview This tutorial explains the Transformer architecture, including its original encoder-decoder design for translation and the decoder-only variant used for modern language generation. It describes decoder components such as masked multi-head self-attention, feed-forward networks, layer normalization, and residual connections, and introduces the Pre-LayerNorm pattern. ### Source excerpt A single 2017 research paper changed the future of AI forever and gave rise to multiple unicorn companies. ## Why JOIN USING Can Lead to Errors in SQL DevFeed: [Why JOIN USING Can Lead to Errors in SQL]() Original publisher: [Read original article]() Author: lukaseder Published: 2026-05-04T14:02:39Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases](), [PostgreSQL]() Tags: [audit-columns](), [errors](), [join](), [postgresql](), [production](), [schema](), [sql](), [statement](), [syntax](), [table]() ### AI overview The article explains why JOIN USING and NATURAL JOIN can make SQL queries fragile as schemas evolve. Adding a same-named column can introduce ambiguity or change join behavior, causing existing queries to fail, so explicit join conditions are recommended for production queries. ### Source excerpt Some SQL operators are as esoteric as they're powerful. One of the oldest operator that you've likely hardly ever used in real world applications is NATURAL JOIN which is the default in relational algebra. We've covered a funky use-case for NATURAL JOIN earlier on this blog. The main reason why it's not very useful is ... Continue reading Why JOIN USING Can Lead to Errors in SQL -> ## Comparing Python and Kotlin for Backend Development DevFeed: [Comparing Python and Kotlin for Backend Development]() Original publisher: [Read original article]() Published: 2026-03-09T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Python](), [backend-development](), [Development]() Tags: [backend-development](), [bugs](), [concurrency](), [inheritance](), [kotlin](), [python](), [switching](), [syntax](), [workshop-learning-programming]() ### AI overview The article compares Python and Kotlin for backend development, explaining why teams may switch to Kotlin and examining differences in performance, type and mutability safety, concurrency, syntax, and default arguments. ### Source excerpt Exploring the benefits of switching from Python to Kotlin for modern backend development. ## What Happens to an SQL Query? DevFeed: [What Happens to an SQL Query?]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-03-04T03:14:28Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [SQL](), [Databases](), [Parser](), [syntax]() Tags: [database](), [diagram](), [errors](), [execution](), [locks](), [rollback](), [sql](), [syntax]() ### AI overview This tutorial explains how an SQL query moves through a database. It covers transport and access checks, parsing and optimization into an execution plan, execution through the storage engine, and supporting components such as transactions, locks, buffering, and recovery. ### Source excerpt The Journey Through the DB ## The experimental CSS border-shape property for non-rectangular elements DevFeed: [The experimental CSS border-shape property for non-rectangular elements]() Original publisher: [Read original article]() Published: 2026-02-19T00:00:00Z Content type: tutorial Language: en Sources: [Una Kravets]() Topics: [CSS](), [Web platform](), [Chrome Canary](), [browser]() Tags: [chrome-canary](), [code](), [css](), [demo](), [experimental](), [property](), [syntax](), [web-platform]() ### AI overview This article introduces the experimental CSS border-shape property, which defines custom border geometry for non-rectangular elements. It explains how backgrounds, borders, outlines, and shadows follow the new shape, compares it with border-radius, and demonstrates creating tooltips with a fallback. ### Source excerpt Learn about new geometry capabilities with this game-changing experimental CSS feature. ## Split Diffs are Here DevFeed: [Split Diffs are Here]() Original publisher: [Read original article]() Author: Cole Miller Published: 2026-02-18T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Code](), [Git](), [ui]() Tags: [code](), [feature](), [files](), [git](), [scale](), [sync](), [syntax](), [ui]() ### AI overview Zed introduces split diffs as the default in version 0.224. The article explains how the feature uses two multibuffers, reuses the old file versions and syntax trees, and inserts spacers to keep corresponding lines aligned while reviewing changes across multiple files. ### Source excerpt View your code changes in a split diff view in Zed. ## Range-Over Functions in Go DevFeed: [Range-Over Functions in Go]() Original publisher: [Read original article]() Published: 2026-02-16T00:00:00Z Content type: article Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Programming language](), [Programming](), [Data structures]() Tags: [ardan-labs](), [blog](), [code](), [examples](), [generators](), [go](), [go-programming](), [golang](), [programming](), [programming-language](), [syntax]() ### AI overview This article explains Go's range-over-functions experiment, which proposes a standardized iterator model while preserving the familiar for range syntax. It introduces the iter package and sequence abstractions, compares iteration patterns, and uses stack examples to show how iterator logic can be implemented. ### Source excerpt Iteration has long been one of the more fragmented areas of Go, with developers relying on ad hoc patterns to traverse custom data structures. This article explores the range-over-functions experiment, a proposed evolution of the language that introduces a standardized iterator model while preserving Go's familiar for range syntax. Using the new iter package and sequence abstractions, it shows how iteration logic can be expressed more clearly, flexibly, and idiomatically. Originally published in April 2024, the concepts remain highly relevant as Go continues to evolve toward more expressive yet simple language features. ## AI-Augmented Development Does Not Eliminate the Craft of Software DevFeed: [AI-Augmented Development Does Not Eliminate the Craft of Software]() Original publisher: [Read original article]() Author: Scott Hanselman Published: 2026-02-09T05:50:59Z Content type: opinion Language: en Sources: [Scott Hanselman]() Topics: [coding](), [Development](), [Software](), [Artificial Intelligence]() Tags: [ai](), [coding](), [development](), [musings](), [software](), [syntax]() ### AI overview The author argues that AI-augmented development may produce impressive results and change how developers work, but software remains difficult and still requires craftsmanship, good judgment, and the ability to build cohesive systems. ### Source excerpt The Japanese are really good at woodworking. And I love watching the Yankee workshop, my dad makes Native American bows and arrows completely from scratch in his workshop with trees that he finds. This is all different from the stuff you get at IKEA, but I've been coding now for money for 35 years and systems are still complicated, computers still do dumb stuff, humans still do dumb stuff, this is just like the move from assembler to C, like the introduction of syntax highlighting, the introduction of intellisense, and the copy paste directly into production shift when stack overflow happened. There is value in good taste, there is value in craftsmanship, and there is value in human judgment. The furniture might be differently designed, but we're still interior designers and putting together a cohesive system is non-trivial. Don't let them gaslight you with one shot Minecraft clones and one shot C compilers. Software is still hard, it's just that you're no longer I/O bound with the speed of your fingertips. I think that there will be lots of work for us cleaning up after the slop, but if you know what you're doing AI augmented development is going to get you some amazing results and I am enjoying learning a ton during this momentous era shift - but the craft still exists. © 2025 Scott Hanselman. All rights reserved. ## Nice and Naughty Cases of Pattern Matching DevFeed: [Nice and Naughty Cases of Pattern Matching]() Original publisher: [Read original article]() Author: Cay Horstmann Published: 2025-12-08T02:02:26Z Content type: article Language: en Sources: [Java Advent Calendar]() Topics: [Java](), [Programming](), [Code]() Tags: [2025](), [article](), [enums](), [exhaustive](), [expression](), [interfaces](), [java](), [java-language](), [pattern-matching](), [patterns](), [programming](), [sealed](), [statement](), [syntax](), [types]() ### AI overview This article examines Java pattern matching in switch and instanceof, explaining when it fits data-oriented programming, when it becomes an antipattern, and how it interacts with legacy behavior. It uses sealed interfaces, records, enums, and JSON values to illustrate exhaustive pattern matching. ### Source excerpt Since Java 14, the Java switch and instanceof statements have been enhanced, in multiple phases, to support pattern matching and a "data-oriented" programming style. In this article, I explore when this programming style is beneficial, and why. I look at the sweet spot of perfect pattern usage, absolute antipatterns where it should not be used, [...] The post Nice and Naughty Cases of Pattern Matching appeared first on JVM Advent. ## Zed Has Rainbow Brackets DevFeed: [Zed Has Rainbow Brackets]() Original publisher: [Read original article]() Author: Kirill Bulatov Published: 2025-12-03T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Tree-sitter](), [Syntax Highlighting](), [vs-code](), [Refactoring]() Tags: [build](), [feature](), [refactoring](), [rust](), [syntax](), [vs-code]() ### AI overview Zed introduces rainbow brackets, a feature that colors each nesting level differently to help users follow matching brackets. The article explains how Zed implemented it using tree-sitter queries and existing language-extension query files rather than maintaining complete syntax trees in memory. ### Source excerpt A whole new world of color comes to Zed. ## IOS/XR Route Redistribution Configuration Mess DevFeed: [IOS/XR Route Redistribution Configuration Mess]() Original publisher: [Read original article]() Published: 2025-11-24T06:43:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Cisco](), [Routing (disambiguation)](), [configuration](), [Network](), [BGP](), [IS-IS](), [networking]() Tags: [bgp](), [boot](), [cisco](), [configuration](), [is-is](), [netlab](), [network](), [ospf](), [protocol](), [routing](), [syntax](), [tests]() ### AI overview This article examines route redistribution on Cisco IOS/XR, showing that OSPFv2/OSPFv3, IS-IS, and BGP use inconsistent syntax for the source protocol in redistribute commands. The inconsistencies make reusable configuration templates more difficult to create. ### Source excerpt One would hope that the developers of a network operating system wouldn't feel the irresistible urge to reinvent what should have been a common configuration feature for every routing protocol. Alas, the IOS/XR developers failed to get that memo. I decided to implement route redistribution (known as route import in netlab) for OSPFv2/OSPFv3, IS-IS, and BGP on IOS/XR (Cisco 8000v running IOS/XR release 24.4.1) and found that each routing protocol uses a different syntax for the source routing protocol part of the redistribute command. Read more ... ## Range Syntax for Style Queries DevFeed: [Range Syntax for Style Queries]() Original publisher: [Read original article]() Published: 2025-11-12T00:00:00Z Content type: tutorial Language: en Sources: [Una Kravets]() Topics: [CSS](), [Web Development](), [Code]() Tags: [css](), [demo](), [example](), [function](), [how-to](), [learn](), [properties](), [range](), [syntax]() ### AI overview A tutorial on using range syntax in CSS style queries and the if() function. It explains comparisons involving custom properties, literal values, and function results, with examples for responsive components, weather cards, grid placement, and styling effects. ### Source excerpt Learn how to use the new range syntax for CSS style queries and the if() function. ## Compiling a Call to a Block DevFeed: [Compiling a Call to a Block]() Original publisher: [Read original article]() Author: Pat Shaughnessy Published: 2025-11-03T00:00:00Z Content type: tutorial Language: en Sources: [Pat Shaughnessy]() Topics: [Ruby](), [Compiler](), [Parser](), [Code](), [Programming]() Tags: [code](), [compiler](), [language](), [ruby](), [syntax](), [updating-ruby-under-a-microscope]() ### AI overview An excerpt from a revised edition of Ruby Under a Microscope explains how Ruby's compiler handles a call to the 10.times method with a block. It examines the Prism parser's redesigned abstract syntax tree and the corresponding YARV instruction generation. ### Source excerpt I've started working on a new edition of Ruby Under a Microscope that covers Ruby 3.x. I'm working on this in my spare time, so it will take a while. Leave a comment or drop me a line and I'll email you when it's finished. This week's excerpt ## Parsing: How Ruby Understands Your Code DevFeed: [Parsing: How Ruby Understands Your Code]() Original publisher: [Read original article]() Author: Pat Shaughnessy Published: 2025-10-27T00:00:00Z Content type: article Language: en Sources: [Pat Shaughnessy]() Topics: [Parsing](), [Ruby](), [Parser](), [syntax](), [tokenization](), [Code](), [Algorithm]() Tags: [algorithm](), [code](), [parsing](), [ruby](), [syntax](), [tokenization](), [updating-ruby-under-a-microscope]() ### AI overview This excerpt explains how Ruby parses source code after tokenization. It describes syntax matching, recursive parsing of subexpressions, and syntax errors when no pattern matches. ### Source excerpt I've started working on a new edition of Ruby Under a Microscope that covers Ruby 3.x. I'm working on this in my spare time, so it will take a while. Leave a comment or drop me a line and I'll email you when it's finished. Update ## vimrc: settings based on terminal background DevFeed: [vimrc: settings based on terminal background]() Original publisher: [Read original article]() Published: 2025-09-05T17:22:45Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [Syntax Highlighting](), [Terminal]() Tags: [based](), [highlighting](), [how-to](), [set](), [settings](), [syntax](), [syntax-highlighting](), [terminal]() ### AI overview A tutorial on configuring Vim syntax-highlighting colorschemes based on the current terminal background. ### Source excerpt How to set e.g., syntax highlighting colorschemes based on the current terminal's background. ## A Lean Syntax Primer DevFeed: [A Lean Syntax Primer]() Original publisher: [Read original article]() Published: 2025-09-02T00:00:00Z Content type: tutorial Language: en Sources: [Dan Abramov]() Topics: [Lean](), [syntax](), [Programming](), [Code]() Tags: [code](), [how-to](), [learn](), [programming](), [syntax](), [types]() ### AI overview An opinionated introduction to Lean syntax covering definitions, assignment and comparison syntax, type inference, explicit type annotations, natural numbers, integers, and running code in the online playground or VS Code. It also introduces the distinction between executing Lean code and proving facts about it. ### Source excerpt Programming with proofs. [Next page]()