# reactive Reactive processing is a programming paradigm for building non-blocking, asynchronous applications with back-pressure. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Closing the IPv6 First-Packet Gap with GRAND DevFeed: [Closing the IPv6 First-Packet Gap with GRAND]() Original publisher: [Read original article]() Author: Seyed Pouria Mousavizadeh Tehrani Published: 2026-09-04T13:32:29Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Network](), [Internet](), [reactive](), [Latency]() Tags: [competition](), [internet](), [ipv6](), [latency](), [network](), [open-source](), [reactive]() ### AI overview The article explains an IPv6 Neighbour Discovery asymmetry: a host can reach its router immediately after configuring an address, while the router may not yet know how to reach the host. This can delay or drop the first return packets. GRAND addresses the gap by having the host proactively advertise its address, and the article describes an implementation of this mechanism in FreeBSD. ### Source excerpt There is a subtle asymmetry in IPv6 Neighbour Discovery: a host knows how to reach its router before the router necessarily knows how to reach the host. GRAND fixes that asymmetry by making the host proactively advertise its address, and I implemented that mechanism in FreeBSD. ## Styling Mastery and Declarative Form Submissions DevFeed: [Styling Mastery and Declarative Form Submissions]() Original publisher: [Read original article]() Author: Angular Published: 2026-08-28T11:01:01Z Content type: article Language: en Sources: [Angular]() Topics: [Angular](), [Forms](), [CSS](), [reactive]() Tags: [angular](), [css](), [deep-dive](), [forms](), [reactive](), [reactive-forms](), [tutorial]() ### AI overview An Angular community roundup featuring resources on component CSS and styling architecture, Reactive Forms validation and data structures, and declarative form submissions with the formRoot directive in Angular v21. ### Source excerpt The Angular ecosystem continues to evolve with powerful new form primitives, styling best practices, and AI-assisted workflows. This week, our global community experts bring us deep dives into component CSS and declarative form handling. Check out this week's expert-led resources: Mastering CSS in Angular (Spanish with English Subtitles) Alejandro Cuba Ruiz (@zorphdark), Raul Jiménez, and Rafael Mestre (@mestre_dev) team up for a fantastic discussion on styling architecture. Learn best practices for managing component styles, encapsulation, and modern CSS patterns in Angular apps. Watch the discussion: https://youtu.be/YrY3tgbkJkY Free Book Chapter: Deep Dive into Reactive Forms (German) Johannes Hoppe (@johanneshoppe) , Ferdinand Malcher (@fmalcher01), and Danny Koppenhagen have released another valuable free excerpt from their upcoming book! This chapter provides an incredibly thorough guide to managing complex validation and data structures using traditional Reactive Forms. Read the free chapter: https://angular-buch.com/material/reactive-forms Signal Forms: Declarative Submission with formRoot (French) Modeste Assiongbon (@rblmdst) continues his exceptional French-language coverage of Angular v21. This installment walks through how to utilize the new formRoot directive to handle form submissions in a clean, declarative manner. Watch the French tutorial: https://youtu.be/um7SYqXcGA8 Keep the knowledge moving! Use #AngularSparkles to share your favorite tutorials and level up your fellow developers. Styling Mastery and Declarative Form Submissions 🎨🤖 was originally published in Angular Blog on Medium, where people are continuing the conversation by highlighting and responding to this story. ## Angular Forms, Web AI, and Architecture Community Features DevFeed: [Angular Forms, Web AI, and Architecture Community Features]() Original publisher: [Read original article]() Author: Angular Published: 2026-08-14T13:01:03Z Content type: article Language: en Sources: [Angular]() Topics: [Angular](), [Forms](), [Artificial Intelligence](), [Web](), [reactive](), [Development](), [Tooling]() Tags: [ai](), [angular](), [angular-newsletter](), [angular-weekly](), [coding](), [forms](), [state](), [state-management](), [tooling](), [tutorials](), [web]() ### AI overview This Angular community roundup covers the evolution of form state management from template-driven approaches to the reactive Signal Forms API, client-side machine learning in browsers, Angular v21 architecture, pragmatic AI use, developer tooling, and coding challenges involving Signal Forms and form arrays. ### Source excerpt The Angular ecosystem continues to push forward with deeper AI integration and modern form architectures. This week, our community experts track the complete evolution of form handling, explore client-side AI, and dive into tactical discussions about developer craftsmanship in the age of AI. Catch up with these incredible community features! From Template-Driven to Signal-Driven Angular Forms Sonu Kapoor @SonuKapoor1978 charts the complete architectural evolution of forms in Angular. Learn how form state management has progressed from legacy template-driven approaches all the way to the highly reactive, modern Signal Forms API. Read the full article: https://www.codemag.com/Article/264041/From-Template-Driven-to-Signal-Driven-The-Complete-Evolution-of-Angular-Forms What's New in Web AI? Christian Liebel (@christianliebel) l breaks down the latest advancements in client-side machine learning. Discover how you can leverage powerful Web AI capabilities directly inside browser environments to build faster, privacy-focused web experiences. Watch the conference talk: https://www.youtube.com/watch?v=jFd8FomARsw The Dev Life Podcast: Angular v21 Architecture, Pragmatic AI, and Tooling Lessons Brooke Avery @JediBravery and Matthew Christiansen drop three stellar episodes of The Dev Life podcast covering architecture and real-world AI strategies. First, they host Sander Elias to map out v21 vision and velocity from an architect's lens. Next, legendary author Dave Thomas drops by to discuss developer craftsmanship as a "Pragmatic Agent." Finally, Alfredo Perez joins the show to share favorite tools and hard-earned lessons from using AI in the trenches. Listen to Ep. 11 (Modern Angular Architecture): https://www.youtube.com/watch?v=r0bKFy96UMM Listen to Ep. 13 (The Pragmatic Agent): https://www.youtube.com/watch?v=-rGMJdbH-yA Listen to Ep. 16 (AI in the Trenches): https://www.youtube.com/watch?v=bg38uSYpM8c Hands-On Code Challenges: Signal Forms and Form Arrays Ready to practic ## Where I'm Writing Now: The Complete 14-Part BlocSignal Series on DEV.to DevFeed: [Where I'm Writing Now: The Complete 14-Part BlocSignal Series on DEV.to]() Original publisher: [Read original article]() Author: Randal L. Schwartz Published: 2026-08-10T16:00:59Z Content type: opinion Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Dart](), [reactive](), [Dependency injection](), [OpenTelemetry](), [Web Development]() Tags: [bloc](), [blocsignal](), [dart](), [dependency](), [dev](), [developer-community](), [development](), [flutter](), [series](), [signal](), [state-management](), [tracing](), [writing]() ### AI overview The author announces that DEV.to and the Google Developer Experts organization on DEV.to are now the primary publishing hubs for new technical writing. The article presents a 14-part BlocSignal series covering Dart and Flutter state management, architecture, interoperability, dependency injection, tracing, and web development. ### Source excerpt If you've been following my articles here on Medium over the years, thank you! I wanted to share a quick update on where I'm primarily publishing my new technical deep dives, architectural guides, and Flutter/Dart tutorials. Going forward, my primary writing hub is DEV.to (@randalschwartz) and the official Google Developer Experts (GDE) organization on DEV.to. DEV.to provides a vibrant developer community, native Dart syntax highlighting, and a built-in Series feature that links connected articles into structured, multi-part curricula. 🚀 The New Series: BlocSignal Architecture & Practice Over the last month, my team and I launched BlocSignal -- a production-grade state management framework for Dart and Flutter that bridges BLoC's enterprise discipline with Signals' 0ms synchronous reactivity. We've published a comprehensive 14-part series on DEV.to covering everything from core state machine philosophy and Riverpod/Provider interop to dependency injection, OpenTelemetry tracing, and Jaspr web development. Here is the complete roadmap of all 14 articles available to read right now on DEV.to: 🏛 1. Core Architecture & Philosophy Introducing BlocSignal: Unidirectional Data Flow Meets Reactive Signals The origin story: bridging BLoC semantics with Rody Davis's signals v7 primitives for 0ms microtask queue latency. BLoC meets Signals: How to Pitch BlocSignal to Your Dev Leads How to navigate technical team reviews and explain the enterprise value of synchronous signal graphs. How We Achieved Full BLoC API & Protocol Parity in BlocSignal 0.2.0 A deep dive into BlocProvider, BlocBuilder, BlocListener, BlocConsumer, and context.select parity. Beyond ProviderNotFound: How BlocSignal Rethinks State Location and Synchronous Propagation Solving scope lookups and understanding why synchronous signal updates prevent frame tearing. From Raw Signals to BlocSignal: Taming Reactivity for Enterprise Scale How encapsulating signals inside Cubit/Bloc containers stops global signal "spagh ## Angular Weekly: Tutorials and Guides on Reactive Flows, AI Agents, SignalStore Events, and SSR DevFeed: [Angular Weekly: Tutorials and Guides on Reactive Flows, AI Agents, SignalStore Events, and SSR]() Original publisher: [Read original article]() Author: Angular Published: 2026-07-17T10:01:04Z Content type: news Language: en Sources: [Angular]() Topics: [Angular](), [reactive](), [AI Agent](), [Claude Code](), [Forms](), [Accessibility](), [Monitoring](), [Server-side rendering]() Tags: [accessibility](), [ai-agent](), [angular](), [angular-weekly](), [claude-code](), [forms](), [monitoring](), [reactive](), [server-side-rendering]() ### AI overview This Angular community roundup highlights tutorials and guides on Modern Angular, Claude Code for Angular development, NgRx SignalStore events, signal-driven error monitoring, accessible Signal Forms, reactive flows, and Angular 21 server-side rendering. ### Source excerpt The Angular ecosystem is moving incredibly fast, bringing together fully reactive architectures, smart AI agents, and robust state management. Whether you're starting from scratch or optimizing enterprise applications, our community has you covered with exceptional resources this week! Dive into these latest expert-led contributions: Modern Angular from Scratch (French) Modeste Assiongbon (@rblmdst) has launched an extensive, practical step-by-step tutorial series designed to help the French-speaking community master Modern Angular (v19+) completely from zero. Start the playlist: https://www.youtube.com/playlist?list=PLnBtvYS1AbOy9MbzptICj-qH4rIat7j9M Claude Code: The AI Agent for Angular Developers Johannes Hoppe (@johanneshoppe) explores how to integrate Claude Code into your development pipeline. Learn how this specialized command-line AI agent acts as a powerful companion for both seasoned developers and newcomers. Read the blog post: https://angular.schule/blog/2026-02-claude-code NgRx SignalStore Events Plugin (English & Spanish) Arcadio Quintero (@oidacra) introduces a game-changing plugin for managing SignalStore events. Discover how to handle side effects cleanly and pass explicit event signals directly into your application state. Read the English guide: https://arcadioquintero.com/en/blog/ngrx-signalstore-events-plugin Read the Spanish guide: https://arcadioquintero.com/es/blog/ngrx-signalstore-events-plugin Signal-Driven Error Monitoring in Angular Sonu Kapoor (@SonuKapoor1978) breaks down how to detect and debug reactive failures. This guide shows you how to implement Signal-driven error monitoring to catch bugs gracefully across your asynchronous streams. Read the technical deep-dive: https://blog.appsignal.com/2026/02/19/signal-driven-error-monitoring-detecting-and-debugging-reactive-failures-in-angular.html Angular v21 Signal Forms: FocusBoundControl (French) Modeste Assiongbon (@rblmdst) delivers a targeted tutorial focusing on form accessibility an ## How We Cut Kafka Consumer Deployment Costs by 83% DevFeed: [How We Cut Kafka Consumer Deployment Costs by 83%]() Original publisher: [Read original article]() Author: ZhongLi Shen He creates fantastic software as a backend engineer GitHub profile Linkedin profile Published: 2026-06-12T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [Kafka](), [Deployer](), [Deployment](), [reactive](), [Library]() Tags: [backend](), [backpressure](), [debugging](), [deployment](), [engineering](), [infrastructure](), [java](), [kafka](), [library](), [performance](), [reactive]() ### AI overview This post explains how trivago investigated PSE-kafka's low CPU usage, slow Kafka polling, and consumer lag. The investigation found that replacing the in-house KafkaReceiverFlux with spring-kafka removed the lag, while the team continued looking for a suitable fix that preserved pull-based consumption and backpressure. The changes ultimately cut infrastructure costs by 83% and ended a run of 19 P1 incidents. ### Source excerpt This post walks through a layered performance investigation that cut PSE-kafka's infrastructure costs by 83% and ended a run of 19 P1 incidents.PSE-kafka (price-search-engine-kafka) i... ## Announcing Angular v22 DevFeed: [Announcing Angular v22]() Original publisher: [Read original article]() Author: Angular Published: 2026-06-03T16:14:58Z Content type: release Language: en Sources: [Angular]() Topics: [Angular](), [Forms](), [aria](), [reactive](), [angular material]() Tags: [angular](), [angular-material](), [angular-release](), [angular-v22](), [new-features](), [quality](), [reactive-forms](), [release]() ### AI overview Angular v22 is released with updates focused on stability and developer ergonomics. The release moves Signal Forms, Angular Aria, and the Asynchronous Reactivity APIs to production-ready status. Signal Forms also receive documentation, community feedback updates, and Angular Material and Angular Aria integration support. ### Source excerpt Today, we are thrilled to announce the release of Angular v22. We continue to be proud of the work we do with each release. Our goal is to maintain a high quality stream of features and improvements that make the workflows for developers smooth no matter how they build Angular applications. Angular is the solid foundation upon which you can build what's next on the web. This release features updates across stability, ergonomics and more. We want Angular to be a sort of launch pad that you can use as you build your next great application. There's some great features to discuss, so let's dive in. Production Ready is the Name of the Game On the Angular team, we take a lot of joy and pride in our ability to update our APIs to bring great new features to Angular. When bringing new features to the table, we typically release a feature as experimental or developer preview. This gives the team time to gather feedback and iterate on new features. During this time, features will undergo refinement with the intention of delivering the best possible version to the community. This is great except that it means some features will not be production ready even though developers are excited and ready to use them immediately. In this release, we're excited to be bringing 3 significant Angular features to production-ready, stable status: Signal Forms, Angular Aria and the Asynchronous Reactivity APIs. Signal Forms: Composable, Reactive and Ready to go We designed Signal Forms to be the new, robust forms API. Signal forms combine the best parts of Reactive forms, the value of strongly typed forms, as well as the things developers love about template driven forms and reactivity of signals. We put all of that together to make a reactive, composable and declarative form solution. When we launched Signal Forms in v21, we received strong signals (pun intended) from teams inside and outside of Google that we were on the right track. Since then, we've updated Signal Forms by: Adding a complet ## strace-ui, Bonsai\_term, and the TUI renaissance DevFeed: [strace-ui, Bonsai\_term, and the TUI renaissance]() Original publisher: [Read original article]() Author: James Somers Published: 2026-05-26T00:00:00Z Content type: article Language: en Sources: [Jane Street]() Topics: [Text-based user interface](), [Terminal](), [debug](), [tracing](), [OCaml](), [reactive](), [Bonsai](), [Library]() Tags: [debugging](), [framework](), [functional](), [library](), [ocaml](), [reactive](), [terminal](), [threads](), [trace](), [ui]() ### AI overview The article introduces strace-ui, an interactive terminal UI that makes strace output easier to inspect by formatting data, assigning short identifiers to processes and threads, and supporting interactive filtering and navigation. It also discusses how OCaml and the Bonsai framework have made interactive terminal UI development more practical. ### Source excerpt We've always found strace useful but somewhat hard to work with. Its output is often inscrutable, it's hard to follow subprocesses or threads, and if you want to filter syscalls you have to rerun the trace with a flag for each one. What you want in debugging is a tool for exploring, refining, etc., but strace can make this difficult. ## Realtime PostgreSQL: From Data Connect to SQL Connect DevFeed: [Realtime PostgreSQL: From Data Connect to SQL Connect]() Original publisher: [Read original article]() Author: Cynthia Wang Published: 2026-04-29T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [PostgreSQL](), [SQL](), [Firebase](), [GraphQL](), [Caching](), [reactive](), [SDKs]() Tags: [admin-sdk](), [caching](), [cloud-functions](), [firebase](), [full-text-search](), [graphql](), [postgresql](), [real-time](), [realtime](), [sdks](), [sql](), [sql-connect](), [updates]() ### AI overview Firebase announces that Firebase Data Connect is becoming Firebase SQL Connect, with a renewed focus on PostgreSQL and expanded SQL capabilities. The update includes Realtime Query Updates, Offline Caching, raw SQL alongside GraphQL, and lower-friction access for prototypes and testing. ### Source excerpt News, tutorials, and updates from the Firebase team. ## How we rebuilt the foundations of component instances DevFeed: [How we rebuilt the foundations of component instances]() Original publisher: [Read original article]() Author: Naomi Jung Published: 2026-03-17T20:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Design system](), [reactive](), [systems]() Tags: [architecture](), [component](), [design-systems](), [figma](), [reactive]() ### AI overview Figma describes replacing the decade-old Instance Updater architecture for component instances with a reactive foundation. The change made common operations in large design systems up to 50% faster and supports more dynamic features as components become more complex. ### Source excerpt By replacing a decade-old architecture with a reactive foundation, we made common operations in large design systems up to 50% faster and unlocked a new way to build dynamic features. ## What's new in Svelte: March 2026 DevFeed: [What's new in Svelte: March 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-03-01T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [Svelte](), [reactive](), [Frameworks](), [Netlify](), [Vite]() Tags: [bug](), [frameworks](), [netlify](), [performance](), [reactive](), [releases](), [svelte]() ### AI overview Svelte's March 2026 update covers new features and fixes in Svelte, SvelteKit, and the Svelte CLI. Highlights include TrustedHTML support, server-side error boundaries, improved navigation scroll information, Vite 8 support, Netlify adapter changes, configurable redirects, and a new official better-auth addon. ### Source excerpt This month, we got a ton of new features across Svelte, SvelteKit and even the Svelte CLI. Plus, the State of JS 2025 is out and Svelte continues to hold the top spot among reactive frameworks in terms of positive sentiment. So, without further ado, let's dive in! What's new in Svelte createContext can now be used when instantiating components programmatically (svelte@5.50.0, Docs, #17575) {@html} expressions now support TrustedHTML (svelte@5.52.0, #17701) Comments are now allowed in HTML tags (svelte@5.53.0/svelte-language-server@0.17.28, #17671) Error boundaries now work on the server (svelte@5.53.0, Docs, #17672) For a full list of changes - including all the important bugfixes that went into the releases this month - check out the Svelte compiler's CHANGELOG What's new in SvelteKit hydratable's injected script now works with CSP (kit@2.51.0, #15048) Navigation callbacks (beforeNavigate, onNavigate, and afterNavigate) now include scroll position information via the scroll property on from and to targets. This enables use cases like animating transitions based on the target scroll position when using browser back/forward navigation (kit@2.51.0, Docs, #15248) Vite 8 is now supported (kit@2.53.0, #15024) The match function can map a path back to a route id and params (kit@2.52.0, Docs, #14997) Breaking (Netlify Adapter): platform.context now uses modern Netlify Functions - previously this was the AWS Lambda-style context. If you were using this in your app (unlikely), you will need to update your code to read from new fields. (adapter-netlify@6.0.0, More details, Docs, #15203) redirects can now be configured in netlify.toml - removing the limitation of only being able to configure redirects via the _redirects file (adapter-netlify@6.0.0, #15203) better-auth is now an official addon in the Svelte CLI (sv@0.12.0, #898) Looking for more details on the many bug fixes and performance optimizations from this month? Check out the SvelteKit / Adapter CHANGELOGs. Community S ## afterRenderEffect, afterNextRender, afterEveryRender & Renderer2 DevFeed: [afterRenderEffect, afterNextRender, afterEveryRender & Renderer2]() Original publisher: [Read original article]() Author: Eduard Krivanek Published: 2025-09-16T11:29:19Z Content type: tutorial Language: en Sources: [Daniel Glejzner]() Topics: [Angular](), [Document Object Model (DOM)](), [Server-side rendering](), [reactive]() Tags: [angular](), [articles](), [browser](), [reactive](), [rxjs](), [ssr](), [state]() ### AI overview This Angular tutorial compares effect, afterRenderEffect, afterNextRender, afterEveryRender, and Renderer2. It explains how effects respond to signal dependencies, how they interact with server-side rendering, when browser-only work should run, and how cleanup helps prevent leaks from listeners, intervals, and external libraries. ### Source excerpt Recently I've been playing around with some Angular functionalities, which are: effect, afterRenderEffect, afterNextRender, afterEveryRender and Renderer2. You don't see them used much compared to signals or computed. Maybe only effect is more common, however how and when to use the rest? I wanted to write ## Migrating to Angular Signals DevFeed: [Migrating to Angular Signals]() Original publisher: [Read original article]() Author: Armen Vardanyan Published: 2025-08-27T10:43:56Z Content type: tutorial Language: en Sources: [Daniel Glejzner]() Topics: [Angular](), [reactive]() Tags: [angular](), [articles](), [optional](), [reactive](), [rxjs](), [state](), [state-management]() ### AI overview This tutorial examines migrating Angular applications to Signals for state management and reactivity. It explains that RxJS is expected to become optional rather than unsupported, while Signals can handle many tasks. ### Source excerpt Today, everyone, everywhere in the Angular community is talking about Signals. They are the new way to manage state and reactivity in Angular applications, promising a better way to build logic and a very much improved change detection. However, many are hesitant. And this is understandable! Not only are signals ## TanStack DB with Sync - the future of real-time UI DevFeed: [TanStack DB with Sync - the future of real-time UI]() Original publisher: [Read original article]() Author: Andre Landgraf Published: 2025-08-07T00:14:47Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [real-time](), [reactive](), [Databases](), [WebSocket](), [Server](), [Back end](), [Figma]() Tags: [building](), [community](), [data](), [database](), [developers](), [figma](), [frameworks](), [reactive](), [real-time](), [replication](), [server](), [sync](), [ui](), [web]() ### AI overview The article explains why scalable real-time applications are difficult to build with conventional client-request, server-response web frameworks. It presents sync engines as dedicated services that synchronize distributed client state, connect to databases, use Postgres logical replication to detect changes, and push updates to subscribed clients. ElectricSQL is described as a Postgres-native sync engine that moves real-time logic out of the backend, reducing application complexity and boilerplate while enabling collaborative, multi-device, and multi-user interfaces. ### Source excerpt Multiplayer UIs aren't new. Tools like Figma and Google Docs have brought collaborative, real-time experiences to millions of users. But for most developers, building robust and scalable real-time applications has always been out of reach. Real-time is hard. The benefits are obvi... ## VanillaCreamJS adds reactive capabilities to native JavaScript without build or compilation steps DevFeed: [VanillaCreamJS adds reactive capabilities to native JavaScript without build or compilation steps]() Original publisher: [Read original article]() Author: Riccardo Degni Published: 2025-06-10T15:36:07Z Content type: article Language: en Sources: [Backend Job: skill, salary and insights - Codemotion Magazine]() Topics: [JavaScript](), [Library](), [reactive](), [Document Object Model (DOM)](), [Web Development]() Tags: [backend](), [frameworks](), [javascript](), [library](), [reactive](), [web]() ### AI overview This developer article introduces VanillaCreamJS, a JavaScript library that adds reactive state binding and DOM-update capabilities to native JavaScript without build tools or compilation. It describes installation, the $ function, reactive properties, bulk updates, refs, and support for deep reactivity with arrays, objects, and matrices. ### Source excerpt VanillaCreamJS is a JavaScript library that literally gives "superpowers" to native JavaScript, enabling powerful and modern capabilities like reactivity without the need for build tools or compilation steps. It's a one-of-a-kind technology because it: VanillaCreamJS is created and maintained by Riccardo Degni, a senior Italian web developer. 👉 https://www.riccardodegni.com/projects/vanillacreamjs 📦 Installation Simply include VanillaCreamJS via... Read more The post VanillaCreamJS: Superpowers for Native JavaScript appeared first on Codemotion Magazine. ## Turning Any Android Callback into a Flow with callbackFlow DevFeed: [Turning Any Android Callback into a Flow with callbackFlow]() Original publisher: [Read original article]() Author: Michael Evans Published: 2025-03-23T03:10:16Z Content type: tutorial Language: en Sources: [Gadget Habit]() Topics: [Android](), [Kotlin](), [Coroutines](), [Firebase](), [reactive](), [API](), [Jetpack Compose]() Tags: [android](), [api](), [coroutines](), [firebase](), [jetpack-compose](), [kotlin](), [reactive](), [realtime-database]() ### AI overview This tutorial explains how to use Kotlin's callbackFlow to adapt callback- or listener-based Android APIs into reactive Flow streams. Using Firebase Realtime Database as an example, it shows how to emit updates, propagate cancellation errors, and remove listeners when collection ends. ### Source excerpt If you've been working with Android for any amount of time, you've probably run into APIs that expose their results using callbacks or listeners. Whether it's something like LocationManager, a custom SDK, or a third-party service like Firebase, you're often stuck adapting old-school async patterns into your modern reactive code. This approach is especially helpful in apps using Jetpack Compose, coroutines, or unidirectional data flow. Fortunately, Kotlin's callbackFlow makes this much easier. In this post, we'll show how to wrap a listener-based API using callbackFlow, so you can collect updates as a Flow. We'll use the Firebase Realtime Database as an example, but this pattern works for nearly anything. The Problem: Listeners Aren't Reactive Here's the classic way of listening to changes in the Firebase Realtime Database: 1 2 3 4 5 6 7 8 9 10 11 val postListener = object : ValueEventListener { override fun onDataChange(dataSnapshot: DataSnapshot) { val post = dataSnapshot.getValue() // update UI } override fun onCancelled(error: DatabaseError) { Log.w(TAG, "loadPost:onCancelled", error.toException()) } } postReference.addValueEventListener(postListener) This works fine -- but it's imperative and not easily composable with things like StateFlow, LiveData, or Jetpack Compose. Let's fix that. The Fix: Wrap It with callbackFlow Kotlin's callbackFlow is designed for exactly this kind of situation -- where you need to bridge a listener-based API into a reactive stream. Here's what it looks like for Firebase: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 fun Query.asFlow(): Flow = callbackFlow { val listener = object : ValueEventListener { override fun onDataChange(snapshot: DataSnapshot) { trySend(snapshot).isSuccess // emit each snapshot into the Flow } override fun onCancelled(error: DatabaseError) { close(error.toException()) // cancel the flow on error } } // Start listening for updates addValueEventListener(listener) // Suspend until the flow is closed ## jOOQ 3.20 released with ClickHouse, Databricks, and much more DuckDB support, new modules, Oracle type hierarchies, more spatial support, decfloat and synonym support, hidden columns, Scala 3, Kotlin 2, and much more DevFeed: [jOOQ 3.20 released with ClickHouse, Databricks, and much more DuckDB support, new modules, Oracle type hierarchies, more spatial support, decfloat and synonym support, hidden columns, Scala 3, Kotlin 2, and much more]() Original publisher: [Read original article]() Author: lukaseder Published: 2025-02-20T10:27:54Z Content type: release Language: en Sources: [jOOQ]() Topics: [clickhouse](), [databricks](), [SQL](), [DuckDB](), [modules](), [Oracle Database](), [Kotlin](), [Scala](), [reactive](), [jpa]() Tags: [array](), [clickhouse](), [databricks](), [decfloat](), [dirty-tracking](), [dml-join](), [duckdb](), [hidden-columns](), [jdk-21](), [jooq](), [jooq-3-20](), [jooq-development](), [jpa](), [json](), [kotlin](), [kotlin-2](), [merge](), [modules](), [oracle](), [oracle-plsql-types](), [r2dbc](), [reactive](), [scala](), [scala-3](), [sequences](), [spatial](), [sql]() ### AI overview jOOQ 3.20 introduces experimental ClickHouse and Databricks SQL dialects, improves DuckDB support, adds new integration modules, and expands support for Oracle type hierarchies, spatial features, decfloat, synonyms, hidden columns, Scala 3, and Kotlin 2. ### Source excerpt New dialects: jOOQ 3.20 ships with 2 new experimental dialects: ClickHouse is a fast-moving SQL dialect with a historic vendor-specific syntax that is gradually migrated to a more standards compliant alternative, which is why our support is still experimental. A lot of behaviours differ from what one would expect elsewhere, including NULL handling, which is ... Continue reading jOOQ 3.20 released with ClickHouse, Databricks, and much more DuckDB support, new modules, Oracle type hierarchies, more spatial support, decfloat and synonym support, hidden columns, Scala 3, Kotlin 2, and much more -> ## How to break the cycle of firefighting and build engineering excellence DevFeed: [How to break the cycle of firefighting and build engineering excellence]() Original publisher: [Read original article]() Author: jesalg Published: 2025-01-01T00:00:00Z Content type: tutorial Language: en Sources: [Jesal Gadhia]() Topics: [Development](), [systems](), [reactive]() Tags: [career](), [development](), [engineering](), [engineering-excellence](), [how-to](), [leadership](), [patterns](), [prevent](), [reactive](), [software-development](), [systems]() ### AI overview This article explains how engineering leaders can break out of reactive firefighting by using systems thinking. It introduces the iceberg model, distinguishing visible events from recurring patterns and deeper causes, and argues that identifying persistent patterns can support more proactive engineering practices. ### Source excerpt Exercise better foresight by identifying patterns, pinpointing what makes them persist, and understanding what could prevent it in the future ## Advent of Svelte DevFeed: [Advent of Svelte]() Original publisher: [Read original article]() Author: The Svelte team Published: 2024-12-01T00:00:00Z Content type: article Language: en Sources: [Svelte blog]() Topics: [Svelte](), [Advent of Code](), [Code](), [Accessibility](), [reactive](), [Tutorial]() Tags: [accessibility](), [browser](), [code](), [compiler](), [new-feature](), [reactive](), [svelte](), [tutorial]() ### AI overview Svelte Society's Advent of Svelte presents a daily series of Svelte, SvelteKit, and website improvements released through Christmas. The documented updates include error boundaries, simpler each blocks, exported snippets, configurable form default values, reactive media-query helpers, modern Spring and Tween state alternatives, an accessible hierarchical tutorial menu, binding transformations, documentation links for warnings and errors, and awaited asynchronous SvelteKit startup setup. ### Source excerpt Last December, Svelte Society presented an advent calendar's worth of festive Svelte-themed code challenges. This year, we're turning it around: you get to relax while we take on a challenge. We've set ourselves a goal of releasing one thing a day from here until Christmas, whether it's a new feature in Svelte or SvelteKit or an improvement to the website. Follow @svelte.dev and @sveltesociety.dev and check back every day to see what we've been cooking up. Day 1: error boundaries This is a long-awaited and much-requested feature, that allows you to isolate and recover from errors that occur during rendering. docs tutorial Day 2: each without as If you just want to render something in an {#each ...} block n times, and don't care about the value, you can now omit the as part. docs demo Day 3: exported snippets You can now export snippets from a component's