# DSLs Published articles for DSLs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Article: Your Next DSL Author Is a Language Model DevFeed: [Article: Your Next DSL Author Is a Language Model]() Original publisher: [Read original article]() Author: Irakli Betchvaia Published: 2026-09-16T11:00:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [Large Language Model](), [Infrastructure as code](), [Retrieval Augmented Generation (RAG)](), [Code](), [Fable]() Tags: [ai](), [ai-ml-data-engineering](), [article](), [artificial-intelligence](), [benchmarks](), [development](), [domain-specific-languages](), [dsls](), [hallucinations](), [infrastructure-as-code](), [large-language-model](), [large-language-models](), [ml-data-engineering](), [next-dsl-author-language-model](), [validation]() ### AI overview The article introduces Typed Domain Grounding (TDG), which embeds a domain-specific language as a typed internal DSL in a mainstream host language. It argues that compiler type errors and generate-compile-repair loops can reduce syntactic hallucinations in language-model output. A benchmark reported higher Structural Fidelity and lower hallucination rates than two lenient external DSLs, although first-try compile rates were lower and results varied by model. ### Source excerpt In this article, the author introduces Typed Domain Grounding, an approach to reducing LLM hallucinations in domain-specific languages by embedding them in mainstream typed languages. Using kUML benchmarks and an infrastructure-as-code example, he explores how compiler validation and generate-compile-repair loops can make model-generated DSL output more reliable. By Irakli Betchvaia ## A Failed XML-Based DSL Design Using a Large Regular Expression DevFeed: [A Failed XML-Based DSL Design Using a Large Regular Expression]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-07T06:30:00Z Content type: opinion Language: en Sources: [The Daily WTF]() Topics: [XML](), [Structured-data](), [bug](), [Code]() Tags: [best-of](), [bug](), [code](), [documentation](), [domain-specific-languages](), [dsls](), [regex](), [xml]() ### AI overview The article revisits a failed attempt to build a domain-specific language with XML schemas and a 1,310-character regular expression. It describes a bug in the expression and criticizes the resulting design as an unsuccessful effort to save labor. ### Source excerpt It's a holiday here in the US, a celebration of labor, so we're reaching back through the archives for a story about an attempt to be labor saving that was not successful. Original. --Remy I've had to write a few domain-specific-languages in the past. As per Remy's Law of Requirements Gathering, it's been mostly because the users needed an Excel-like formula language. The danger of DSLs, of course, is that they're often YAGNI in the extreme, or at least a sign that you don't really understand your problem. XML, coupled with schemas, is a tool for building data-focused DSLs. If you have some complex structure, you can convert each of its features into an XML attribute. For example, if you had a grammar that looked something like this: The Source specification obeys the following syntax source = ( Feature1+Feature2+... ":" ) ? steps Feature1 = "local" | "global" Feature2 ="real" | "virtual" | "ComponentType.all" Feature3 ="self" | "ancestors" | "descendants" | "Hierarchy.all" Feature4 = "first" | "last" | "DayAllocation.all" If features are specified, the order of features as given above has strictly to be followed. steps = oneOrMoreNameSteps | zeroOrMoreNameSteps | componentSteps oneOrMoreNameSteps = nameStep ( "." nameStep ) * zeroOrMoreNameSteps = ( nameStep "." ) * nameStep = "#" name name is a string of characters from "A"-"Z", "a"-"z", "0"-"9", "-" and "_". No umlauts allowed, one character is minimum. componentSteps is a list of valid values, see below. Valid 'componentSteps' are: - GlobalValue - Product - Product.Brand - Product.Accommodation - Product.Accommodation.SellingAccom - Product.Accommodation.SellingAccom.Board - Product.Accommodation.SellingAccom.Unit - Product.Accommodation.SellingAccom.Unit.SellingUnit - Product.OnewayFlight - Product.OnewayFlight.BookingClass - Product.ReturnFlight - Product.ReturnFlight.BookingClass - Product.ReturnFlight.Inbound - Product.ReturnFlight.Outbound - Product.Addon - Product.Addon.Service - Product.Addon.ServiceFeatu ## Effective Kotlin Item 46: Avoid member extensions DevFeed: [Effective Kotlin Item 46: Avoid member extensions]() Original publisher: [Read original article]() Published: 2021-07-18T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [function](), [interface]() Tags: [dsls](), [extension-function](), [function](), [integration-test](), [interface](), [kotlin](), [visibility-modifier](), [workshop-learning-programming]() ### AI overview This article explains how Kotlin member extension functions work and why they are generally discouraged. It recommends controlling visibility with visibility modifiers and identifies DSL builders, scope-related functions, and some integration test patterns as appropriate exceptions. ### Source excerpt What member extensions are, how they are possible and why we should avoid using them. ## Creating Kotlin DSLs DevFeed: [Creating Kotlin DSLs]() Original publisher: [Read original article]() Author: Wolfram Rittmeyer Published: 2018-12-29T03:05:09Z Content type: tutorial Language: en Sources: [Grokking Android]() Topics: [Kotlin]() Tags: [android](), [domain-specific-languages](), [dsl](), [dsls](), [extension](), [groovy](), [kotlin](), [languages](), [scala](), [sql](), [tutorials](), [unit-tests](), [yaml]() ### AI overview This article explains how Kotlin can be used to create internal domain-specific languages by combining core language features. It distinguishes internal DSLs from external DSLs and discusses benefits such as concise, readable APIs, with examples including Gradle and KotlinTest. ### Source excerpt Kotlin has many nice things going for it - be it null safety, data classes, extension functions, immutable collections or many other things. For me one additional thing is very interesting: The ability to create domain specific languages (DSLs) easily. Easily, because creating a DSL with Kotlin means that you simply choose to combine several [...] Continue Reading "Creating Kotlin DSLs" The post Creating Kotlin DSLs appeared first on Grokking Android. ## From Java Builders to Kotlin DSLs DevFeed: [From Java Builders to Kotlin DSLs]() Original publisher: [Read original article]() Author: Márton Braun Published: 2018-07-11T06:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [Kotlin](), [Java]() Tags: [builder](), [dsl](), [dsls](), [existing](), [guide](), [java](), [kotlin]() ### AI overview A step-by-step guide to wrapping an existing Java Builder-based API in a neat Kotlin DSL. ### Source excerpt A step by step guide to wrapping an existing Builder-based API into a neat Kotlin DSL. ## Clojure SQL library showdown DevFeed: [Clojure SQL library showdown]() Original publisher: [Read original article]() Published: 2015-12-28T00:00:00Z Content type: comparison Language: en Sources: [Adam Bard]() Topics: [Clojure](), [SQL](), [Library](), [Object-relational mapping]() Tags: [clojure](), [compare](), [dsls](), [jdbc](), [library](), [orm](), [sql]() ### AI overview A comparison of several Clojure SQL DSLs and libraries, including Korma and HoneySQL, against JDBC. The author discusses the trade-offs between writing SQL directly and using abstractions or ORM-style tools. ### Source excerpt When it comes to database access, I've become less particular over the years as I've gotten more and more comfortable with SQL. These days I'm happier to write the SQL to get just the thing I want, than wrestle with an ORM to produce the same thing. Nevertheless, there's something to be said for abstractions over SQL, and they seem to have lasting popularity. In this post, I'll compare a few popular SQL DSLs for Clojure, and contrast them all with their mutual pappy, clojure. ## The Ruby Programming Language DevFeed: [The Ruby Programming Language]() Original publisher: [Read original article]() Author: Tom Published: 2015-08-13T00:00:00Z Content type: article Language: en Sources: [Tomasz Gągor]() Topics: [Ruby](), [Programming language](), [Programming]() Tags: [architecture](), [design-patterns](), [domain-specific-languages](), [dsls](), [internals](), [programming](), [programming-language](), [ruby](), [technology]() ### AI overview A review of The Ruby Programming Language, co-authored by Yukihiro Matsumoto. The book provides a detailed explanation of Ruby's core, architecture, internals, and suitability for building domain-specific languages, but its technical depth makes it difficult for beginners and less practical for day-to-day learning. ### Source excerpt Ruby Programowanie Authors: David Flanagan, Yukihiro Matsumoto I picked up this book, co-authored by Ruby creator Yukihiro "Matz" Matsumoto, to learn Ruby for my work with Chef. As a deep dive into the language's internals, it brilliantly explains why Ruby is a top choice for creating Domain-Specific Languages (DSLs) like those used in Vagrant and Chef. The book meticulously covers the language's core, which gave me a solid understanding of its architecture.