# Declarative programming

A programming paradigm that specifies the desired result while leaving the system to determine how to execute the task.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Web Agents Should Adopt the Compile-and-Execute Paradigm

DevFeed: [Web Agents Should Adopt the Compile-and-Execute Paradigm](<https://devfeed.tech/articles/web-agents-should-adopt-the-compile-and-execute-paradigm-101344.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2605.14290>)

Author: Julien Piet, Annabella Chow, Yiwei Hou, Muxi Lyu, Sylvie Venuto, Jinhao Zhu, Raluca Ada Popa, David Wagner

Published: 2026-10-27T04:00:00Z

Content type: opinion

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [computer-use](<https://devfeed.tech/topics/computer-use.md>), [Web](<https://devfeed.tech/topics/web.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [browser-tools](<https://devfeed.tech/tags/browser-tools.md>), [compile](<https://devfeed.tech/tags/compile.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [interface](<https://devfeed.tech/tags/interface.md>), [planning](<https://devfeed.tech/tags/planning.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [static](<https://devfeed.tech/tags/static.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

The authors argue web agents should default to compile-and-execute: commit to a task-specific program before seeing runtime page content, then run it. ReAct feeds mixed, partly untrusted web content into decisions about the next action, creating a path for prompt injection to steer control flow. A predefined execution graph can let that data affect values or branches without letting it redefine the task or generate new actions. In their WebArena analysis, all tasks were compatible with this approach and 81% could use static programs without runtime LLM calls. Adoption is hindered by browser tools such as click, type, and scroll, whose meanings depend on the page and expose only current-page actions during planning. The authors say the needed infrastructure is typed, complete, auditable website APIs that expose task-level operations and known effects.

### Source excerpt

arXiv:2605.14290v2 Announce Type: replace Abstract: ReAct has become the default architecture across LLM agents, and many existing web agents follow this paradigm. We argue that it is the wrong default for web agents. Instead, web agents should default to compile-and-execute: commit to a task-specific program before observing runtime web content, then execute it. The reason is that web content mixes inputs from many parties. An e-commerce product page may combine a seller's listing, customer reviews, sponsored advertisements, and platform-generated recommendations. Under ReAct, all of this content flows into the model when deciding on the next action, creating a direct path for prompt injections to steer the agent's control flow. Compile-and-execute changes this boundary: untrusted data may influence values or branches inside a predefined execution graph, but it cannot redefine the user task or cause the model to synthesize new actions at runtime. We analyze WebArena, a popular web agent benchmark, and find that all tasks are compatible with compile-and-execute, while 81% can be completed with a purely static program, without any runtime LLM subroutine. We identify the main barrier to adopting compile-and-execute on the web: For it to work well, tools must map cleanly to semantic actions, with effects known before execution, so a compiler has enough information to emit a program. The web does not naturally expose that interface. Browser tools such as click, type, and scroll have page-dependent meanings. Planning at this layer is near-sighted: the agent can only see actions on the current page, and later actions appear only after it acts. Closing this gap requires typed interfaces that turn website interactions from clicks and keystrokes to task-level operations. This is an infrastructure problem, not a modeling problem. Web tasks do not need reactivity by default; they need typed, complete, auditable website APIs.

## Orchestration is More than Scheduling: Declarative Automation in Dagster

DevFeed: [Orchestration is More than Scheduling: Declarative Automation in Dagster](<https://devfeed.tech/articles/orchestration-is-more-than-scheduling-declarative-automation-in-dagster-83711.md>)

Original publisher: [Read original article](<https://dagster.io/blog/orchestration-is-more-than-scheduling-declarative-automation-in-dagster>)

Author: Catherine Noll

Published: 2026-08-06T00:00:00Z

Content type: tutorial

Language: en

Sources: [Dagster](<https://devfeed.tech/sources/dagster.md>)

Topics: [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [dagster](<https://devfeed.tech/tags/dagster.md>), [data-pipelines](<https://devfeed.tech/tags/data-pipelines.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

Dagster's Declarative Automation lets engineers define when data assets should be considered up to date. Dagster evaluates these conditions against asset dependencies, partitions, and execution state to request work. The tutorial demonstrates built-in policies, composed conditions, job-level automation in preview, and isolated tests of automation behavior.

### Source excerpt

Define the outcome, not the orchestration. Declarative Automation lets you express your desired asset state while Dagster continuously handles the work needed to achieve it.

## Simon Peyton Jones on Haskell and Why Functional Programming Matters

DevFeed: [Simon Peyton Jones on Haskell and Why Functional Programming Matters](<https://devfeed.tech/articles/co-creator-of-haskell-functional-programming-thinking-in-types-useless-languages-simon-jones-18084.md>)

Original publisher: [Read original article](<https://www.developing.dev/p/co-creator-of-haskell-functional>)

Author: Ryan Peterman

Published: 2026-06-08T10:02:31Z

Content type: article

Language: en

Sources: [The Developing Dev](<https://devfeed.tech/sources/the-developing-dev.md>)

Topics: [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [Haskell](<https://devfeed.tech/topics/haskell.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>), [Programming language](<https://devfeed.tech/topics/programming-language.md>)

Tags: [declarative](<https://devfeed.tech/tags/declarative.md>), [functional-programming](<https://devfeed.tech/tags/functional-programming.md>), [languages](<https://devfeed.tech/tags/languages.md>), [programming](<https://devfeed.tech/tags/programming.md>), [programming-language](<https://devfeed.tech/tags/programming-language.md>), [types](<https://devfeed.tech/tags/types.md>)

### AI overview

An interview with Simon Peyton Jones, co-creator of Haskell, about functional programming, its emphasis on values rather than mutation, and how it differs from imperative programming.

### Source excerpt

Simon Peyton Jones is the co-creator of Haskell (pure functional programming language) and I interviewed him about functional programming, why it matters, and his thoughts on other programming languages.

## Declarative vs. Imperative Programming: A Practical Guide for Choosing the Right Paradigm

DevFeed: [Declarative vs. Imperative Programming: A Practical Guide for Choosing the Right Paradigm](<https://devfeed.tech/articles/declarative-vs-imperative-programming-a-practical-guide-for-choosing-the-right-paradigm-4459.md>)

Original publisher: [Read original article](<https://www.toptal.com/developers/software/declarative-vs-imperative-programming>)

Author: THOMAS VARGHESE, SENIOR SOFTWARE DEVELOPER @ TOPTAL

Published: 2026-05-05T04:00:00Z

Content type: tutorial

Language: en

Sources: [Toptal](<https://devfeed.tech/sources/toptal-blog.md>)

Topics: [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Code](<https://devfeed.tech/topics/code.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Automation](<https://devfeed.tech/topics/automation.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code](<https://devfeed.tech/tags/code.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [guide](<https://devfeed.tech/tags/guide.md>), [programming](<https://devfeed.tech/tags/programming.md>)

### AI overview

A practical guide to declarative and imperative programming, explaining how each paradigm shapes code structure, application state, debugging, performance, and architectural decisions. It describes the growing use of declarative systems in modern development while noting the complexity hidden behind their abstractions.

### Source excerpt

Deep understanding of declarative versus imperative programming shapes how developers write, run, and maintain code. This guide explains the differences, challenges, and when to choose each approach.

## Swift Result Builders: Creating Custom DSLs for Binary Formatted Data

DevFeed: [Swift Result Builders: Creating Custom DSLs for Binary Formatted Data](<https://devfeed.tech/articles/swift-result-builders-creating-custom-dsls-for-binary-formatted-data-23995.md>)

Original publisher: [Read original article](<https://quickbirdstudios.com/blog/swift-resultbuilder-data/>)

Author: Paul Kraft

Published: 2023-08-03T14:22:38Z

Content type: article

Language: en

Sources: [QuickBird Studios Blog](<https://devfeed.tech/sources/quickbird-studios-blog.md>)

Topics: [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [SwiftUI](<https://devfeed.tech/topics/swiftui.md>), [Bluetooth](<https://devfeed.tech/topics/bluetooth.md>)

Tags: [bluetooth](<https://devfeed.tech/tags/bluetooth.md>), [builder](<https://devfeed.tech/tags/builder.md>), [data](<https://devfeed.tech/tags/data.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [dsls](<https://devfeed.tech/tags/dsls.md>), [ios](<https://devfeed.tech/tags/ios.md>), [networking](<https://devfeed.tech/tags/networking.md>), [post](<https://devfeed.tech/tags/post.md>), [swift](<https://devfeed.tech/tags/swift.md>), [swiftui](<https://devfeed.tech/tags/swiftui.md>)

### AI overview

The excerpt introduces using Swift result builders to describe binary message formats declaratively, so code can handle encoding rather than requiring developers to prescribe each step. It frames this as applying a style familiar from SwiftUI to binary data used in Bluetooth, internet communication, or peer-to-peer networking. The authors say they developed DataKit, a Swift library for declaratively specifying message formats and encoding and decoding binary data. The excerpt ends during its introduction to programming paradigms, so it does not show the builder implementation or its tradeoffs.

### Source excerpt

SwiftUI has revolutionized how we build UI, introducing a more intuitive, declarative approach. Instead of prescribing a series of steps to reach an end goal, we describe the outcome and let the program determine the path The post Swift Result Builders: Creating Custom DSLs for Binary Formatted Data appeared first on QuickBird Studios.

## Graphical Applications in Haskell with FRP and Reflex

DevFeed: [Graphical Applications in Haskell with FRP and Reflex](<https://devfeed.tech/articles/graphical-applications-in-haskell-with-frp-and-reflex-27926.md>)

Original publisher: [Read original article](<http://alt-romes.github.io/posts/lectures/2022-07-10-frp.html>)

Published: 2022-07-10T00:00:00Z

Content type: tutorial

Language: en

Sources: [Romes' Musings](<https://devfeed.tech/sources/romes-musings.md>)

Topics: [Haskell](<https://devfeed.tech/topics/haskell.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [Reflex FRP](<https://devfeed.tech/topics/reflex-frp.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [real-time](<https://devfeed.tech/topics/real-time.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>)

Tags: [functional](<https://devfeed.tech/tags/functional.md>), [functional-programming](<https://devfeed.tech/tags/functional-programming.md>), [haskell](<https://devfeed.tech/tags/haskell.md>), [programming](<https://devfeed.tech/tags/programming.md>), [reactive](<https://devfeed.tech/tags/reactive.md>), [reactive-programming](<https://devfeed.tech/tags/reactive-programming.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [user-interface](<https://devfeed.tech/tags/user-interface.md>)

### AI overview

This article introduces functional reactive programming for interactive graphical user interfaces in Haskell. It explains how behaviours represent values that vary continuously over time and events represent occurrences at particular points in time, allowing programmers to describe reactive systems without handling time-related implementation details directly. The article also covers Reflex and building user interfaces with Reflex-Dom.

### Source excerpt

Contents 1 Functional Reactive Programming 1.1 Behaviours 1.2 Events 2 Reflex 2.1 Building UIs with Reflex-Dom 2.2 Reflex Combinators 3 Example: 101companies 1 Functional Reactive Programming Functional reactive programming is a general paradigm well suited to programming real-time systems in a high-level and functional way. Real-time systems or reactive systems are those that handle continuous time-varying values, discrete events in real time, and react accordingly. A good example of these systems is a mobile robot. They must take into consideration continuous inputs like wheel speed, orientation, and discrete events such as detection of another object. The class of reactive systems we're interested in here is interactive graphical UIs. A user interface has multiple components that can be seen as discrete events and continuous time-varying values. An input box, where one might write their name, is an example of a time varying value (it continously changes - whenever the user types something); a button is an example of a discrete event in time: at certain points in time the user will click the button. This will make more sense with practice and code samples. So the promise of functional reactive programming is that we can program these complicated reactive systems in a pure functional way. But how? Functional Reactive Programming introduces two key concepts: Behaviours and Events. Behaviours are first-class values that vary over continuous time. That means a behaviour is a value that changes with time and can be passed to/returned by functions. Events are first-class values that occur at some points in time. They may refer, e.g., to happenings in the real world time - such as a mouse click or a key press. And then, it says that the FRP implementation will handle all time-related details so that the programmer can describe their reactive system without thinking about what happens at any particular point in time, but rather thinking about what happens accross all poin

## Jetpack Compose 1.0: A Kotlin UI Toolkit for Android

DevFeed: [Jetpack Compose 1.0: A Kotlin UI Toolkit for Android](<https://devfeed.tech/articles/jetpack-compose-1-0-beauty-in-simplicity-touchlab-38230.md>)

Original publisher: [Read original article](<https://touchlab.co/jetpack-compose-stable-kotlin-multiplatform>)

Published: 2021-08-24T04:21:17Z

Content type: article

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Android](<https://devfeed.tech/topics/android.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-open-source-project](<https://devfeed.tech/tags/android-open-source-project.md>), [declarative-programming](<https://devfeed.tech/tags/declarative-programming.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [thoughts](<https://devfeed.tech/tags/thoughts.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Jetpack Compose 1.0 is a stable Kotlin UI toolkit for Android that uses declarative programming to simplify UI development. The article explains how functions transform data into a UI hierarchy and update the view when data changes.

### Source excerpt

Jetpack Compose 1.0 is a UI toolkit written in Kotlin and designed to make life easier for Android developers.

## A Jetpack Compose by any other name

DevFeed: [A Jetpack Compose by any other name](<https://devfeed.tech/articles/a-jetpack-compose-by-any-other-name-20909.md>)

Original publisher: [Read original article](<https://jakewharton.com/a-jetpack-compose-by-any-other-name/>)

Published: 2020-12-30T00:00:00Z

Content type: article

Language: en

Sources: [Jake Wharton](<https://devfeed.tech/sources/jake-wharton.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Android](<https://devfeed.tech/topics/android.md>), [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [React](<https://devfeed.tech/topics/react.md>), [Svelte](<https://devfeed.tech/topics/svelte.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [compose](<https://devfeed.tech/tags/compose.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [programming](<https://devfeed.tech/tags/programming.md>), [react](<https://devfeed.tech/tags/react.md>), [svelte](<https://devfeed.tech/tags/svelte.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

The article examines what Jetpack Compose is, arguing that it should be understood as more than an Android UI toolkit. It describes its origins in declarative Android UI development and the unbundling of platform widgets, while discussing its Kotlin compiler-plugin and DSL foundations, multiplatform scope, and relationship to React and Svelte concepts.

### Source excerpt

I really like Jetpack Compose. Between work and personal stuff I have three projects which are each built on top of it. It's great! So far my biggest problem is its name... but that requires some explaining. Welcome to one of the hills I'll die on! What is Jetpack Compose? If you're already familiar with it, something should pop in your head when asked: What is Jetpack Compose? A new UI toolkit for Android? Yep, that's right. A declarative Android UI framework? Sure, that is correct. A multiplatform application UI? Thanks to JetBrains this is also true. If you're somewhat in tune to how the sausage is made you may also reference the fact that it's a Kotlin compiler plugin and DSL to build Android UI or multiplatform UI. It's those things, too. None of these answers are wrong. However, they're doing a bit of a disservice to the internals of Compose and its unrealized potential. Pedigree What we now know as Jetpack Compose started as two separate projects: The first was a solution for writing declarative Android UIs using the existing platform UI toolkit. Take the declarative components of React, wrap it in an ahead-of-time compiler like Svelte, and target Android's UI toolkit with Kotlin. All existing View-based UI could suddenly level-up by changing their programming paradigm from imperative to declarative. Separately, the toolkit team was about to ramp up on unbundling as many UI widgets as possible from the OS. This followed on the success of ViewPager, RecyclerView, and what was learned from the AppCompat and Design libraries. By removing a ton of OEM touchpoints and normalizing behavior across all versions of Android, the work required to build a good UI would be reduced. Over time these efforts became inescapably linked. If you are building standalone versions of the platform UI widgets then why not take the opportunity to correct mistakes in their API and overcome limitations of the resource system? And if you're changing their API, why not have the new declarat

## Tracking side effects at compile time with suspend

DevFeed: [Tracking side effects at compile time with suspend](<https://devfeed.tech/articles/tracking-side-effects-at-compile-time-with-suspend-27471.md>)

Original publisher: [Read original article](<https://jorgecastilloprz.github.io/tracking-side-effects-with-suspend>)

Author: Jorge Castillo

Published: 2020-10-10T10:00:00Z

Content type: article

Language: en

Sources: [Jorge Castillo](<https://devfeed.tech/sources/jorge-castillo.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>)

Tags: [all-kotlin-posts-including-the-fp-ones](<https://devfeed.tech/tags/all-kotlin-posts-including-the-fp-ones.md>), [android](<https://devfeed.tech/tags/android.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [compose](<https://devfeed.tech/tags/compose.md>), [coroutine](<https://devfeed.tech/tags/coroutine.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [functional-programming](<https://devfeed.tech/tags/functional-programming.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [suspend](<https://devfeed.tech/tags/suspend.md>)

### AI overview

The article explains suspend as a Kotlin standard-library mechanism that makes effects visible to the compiler and restricts them to coroutine environments prepared to execute those effects. It relates this model to deferred execution in Kotlin Sequences and runtime interpretation and optimization in Jetpack Compose.

### Source excerpt

Thinking of suspend as a Kotlin stdlib mechanism for flagging and tracking effects at compile time.

## Find the number of the longest continuously rising days for a stock

DevFeed: [Find the number of the longest continuously rising days for a stock](<https://devfeed.tech/articles/find-the-number-of-the-longest-continuously-rising-days-for-a-stock-34582.md>)

Original publisher: [Read original article](<https://tapoueh.org/blog/2018/02/find-the-number-of-the-longest-continuously-rising-days-for-a-stock/>)

Author: Dimitri Fontaine PostgreSQL Major Contributor; Author

Published: 2018-02-06T22:24:17Z

Content type: comparison

Language: en

Sources: [Dimitri Fontaine](<https://devfeed.tech/sources/dimitri-fontaine.md>)

Topics: [SQL](<https://devfeed.tech/topics/sql.md>), [Declarative programming](<https://devfeed.tech/topics/declarative-programming.md>), [Python](<https://devfeed.tech/topics/python.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [compare](<https://devfeed.tech/tags/compare.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [python](<https://devfeed.tech/tags/python.md>), [sql](<https://devfeed.tech/tags/sql.md>)

### AI overview

The article compares SQL and Python implementations for finding the longest continuously rising sequence of stock-market days and selecting the top 10 records from a billion-row dataset. It argues that SQL's difficulty in these cases is related to its declarative model and the need to understand the data model and business requirements.

### Source excerpt

Today I want to react to an article that claims that Relational Algebra Is the Root of SQL Problems in which the author hand-waves the following position: SQL becomes more a hindrance to data manipulation than an efficient tool. SQL's greatest problem isn't in the implementation level, but at its theory foundation. The problem can't be solved by application optimization. Relational algebra isn't sophisticated enough for handling the complicated data manipulation scenarios. Then they go on to several arguments from authority to "prove" their point. My reading of the article is that SQL is very hard when you didn't care to learn it, as most technologies are. In this article, we're going to look at the simple examples provided where apparently SQL makes it so much harder to find a solution compared to writing some Java or C++ code. Contrary to the original article, we go as far as to actually writing both the SQL solution and a complete Python solution, so that we can compare.