# reload Published articles for reload. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## pproxy: a forward proxy that load-balances a pool of upstream proxies DevFeed: [pproxy: a forward proxy that load-balances a pool of upstream proxies]() Original publisher: [Read original article]() Published: 2026-06-22T00:00:00Z Content type: article Language: en Sources: [Andika Ahmad Ramadhan -- Blog]() Topics: [proxy](), [client](), [health checks](), [HTTP]() Tags: [client](), [health](), [health-checks](), [http](), [prometheus](), [proxy](), [reload](), [round-robin](), [socks5](), [tls]() ### AI overview This article presents pproxy, a forward proxy that distributes client traffic across upstream proxies. It describes active health checks, round-robin selection, failover within requests, hot configuration reloads, per-user authentication, and Prometheus metrics. ### Source excerpt pproxy is a forward proxy that load-balances client traffic across a pool of upstream proxies with active health checks and hot config reload, so switching proxy providers means editing one config file instead of every client. ## Minimal setup for Compose Desktop DevFeed: [Minimal setup for Compose Desktop]() Original publisher: [Read original article]() Published: 2025-12-22T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [compose-for-desktop](), [Compose](), [Kotlin](), [ui]() Tags: [compose](), [desktop](), [fonts](), [how-to](), [icons](), [kotlin](), [material3](), [reload](), [resources](), [setup](), [ui](), [workshop-learning-programming]() ### AI overview A tutorial on setting up Compose Desktop for a minimal desktop application or script UI. It covers required Kotlin and Compose plugins and dependencies, optional Hot Reload, Material3 and Resources, resource organization, desktop preview limitations, and starter application code. ### Source excerpt How to setup Compose to use it on desktop, for providing UI for scripts or a simple project. ## Using Compose Hot Reload to Build a Vaporwave-Inspired Compose Desktop Project DevFeed: [Using Compose Hot Reload to Build a Vaporwave-Inspired Compose Desktop Project]() Original publisher: [Read original article]() Published: 2025-06-09T10:52:55Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [compose-hot-reload](), [Compose](), [Kotlin](), [Gradle](), [multiplatform](), [repo]() Tags: [animate](), [code](), [compose](), [compose-hot-reload](), [gradle](), [kotlin](), [multiplatform](), [reload](), [repo](), [vaporwave]() ### AI overview An exploratory tutorial on using JetBrains Compose Hot Reload in a Compose Desktop project, with Vaporwave as the visual theme. It covers project setup, Kotlin 2.1.20 or later, plugin configuration, the foojay resolver, and running the application. ### Source excerpt Why I want to play with the recently released Compose Hot reload feature by JetBrains. To do this I setup a Desktop compose project and picked a topic to draw and explore: Vaporwave Why? because Vaporwave is a curious Internet thing. It has a strong visual aesthetic that I wanted to recreate. It is intriguing. It is seems to be a fleeting transient phenomena: it is in the name vapor and wave and yet... and yet we see it pop up in unexpected places. It is a form of hauntology: a cultural idea that returns from the past to haunt the present. There will be ramblings interspersed and remixed with code, I will put the code at the beginning of the sections, so that you can easily skim if remix-rambling is not your thing. Yes, there is a matching repo. Yes, it is a mix of organic hand coding and AI enhancements. I will explain my process. But first Setting up Hot Reload You need: A project that has a Compose desktop part. It can be stand alone or part of a multiplatform project Use a Kotlin version 2.1.20 or later Get the plugin and the latest version information and add it the place you keep your versions, like a toml file Setup the plugin in your build.gradle.kts Setup the foojay resolver Run the main application from the gutter icon or command line. something like ./gradlew runHot --mainClass MainKt --auto Optional extra make a run target for your particular main application if you have more than one See and example of each line in the sample repo Wow these instructions are vague! indeed things change quickly. Please follow the original repo. This post will date. Origins and Sound track Vaporwave appeared as a music genre with a strong aesthetic, some say in 2010. The iconic album Floral Shoppe by Macintosh Plus is still available and makes a perfect sound track for inspecting the code or reading this article. Go ahead click the link and start the music. I'll wait. We are on the cusp of widespread changes in how we interact with technology. Will we have nostalgia for the ## What the Android ecosystem could learn from Flutter DevFeed: [What the Android ecosystem could learn from Flutter]() Original publisher: [Read original article]() Author: Cláudia Published: 2023-10-11T13:22:22Z Content type: opinion Language: en Sources: [Blog - Bloco]() Topics: [Flutter](), [Android](), [android-development](), [Jetpack Compose](), [Mobile]() Tags: [android](), [android-development](), [animations](), [bug-fixes](), [compose](), [development](), [flutter](), [jetpack-compose](), [reload](), [team](), [work]() ### AI overview An opinion piece compares Flutter with native Android development, focusing on Flutter's hot reload and widget ecosystem. It argues that Android development could benefit from more immediate code updates and a more unified set of UI components, while noting comparable capabilities in Jetpack Compose. ### Source excerpt We recently had the opportunity to work with Flutter on a project. Here's our honest opinion of the advantages of Flutter that we would like to see in Android development. ## Spin watch - live reload for Wasm app development DevFeed: [Spin watch - live reload for Wasm app development]() Original publisher: [Read original article]() Author: Tim McCallum Published: 2023-06-09T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Development](), [wasm](), [App]() Tags: [app-development](), [applications](), [article](), [development](), [live](), [reload](), [wasm]() ### AI overview This article explains how to configure Spin applications to rebuild or restart automatically when applicable files change, enabling live reloading for Wasm app development. ### Source excerpt This article shows how Spin applications can be configured to rebuild and/or restart whenever changes to applicable files occur. ## Operator-style Prometheus config segregation DevFeed: [Operator-style Prometheus config segregation]() Original publisher: [Read original article]() Published: 2023-01-15T00:00:00Z Content type: tutorial Language: en Sources: [Andika Ahmad Ramadhan -- Blog]() Topics: [Prometheus](), [Monitoring](), [Kubernetes](), [Deployment]() Tags: [combines](), [config](), [files](), [kubernetes](), [prometheus](), [reload](), [server](), [sidecar]() ### AI overview This article introduces prometheus-config-merger, a tool that combines selected configuration fields from an existing Prometheus setup with configuration generated by prometheus-operator. It supports one-shot operation and watch-and-reload mode, including deployment as a Kubernetes sidecar. ### Source excerpt prometheus-config-merger combines config files from your existing Prometheus server and prometheus-operator into one, so you get per-team config segregation without handing your Prometheus over to the operator. ## Speeding Up Tailwind CSS Builds DevFeed: [Speeding Up Tailwind CSS Builds]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-10-13T12:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Tailwind CSS](), [build times](), [PostCSS](), [Development](), [Web Development]() Tags: [build](), [build-times](), [builds](), [css](), [development](), [frontend](), [how-to](), [insights](), [learn](), [live](), [local](), [magnitude](), [make](), [module](), [optimize](), [orders](), [performance](), [postcss](), [reload](), [replacement](), [tailwind](), [times]() ### AI overview A tutorial on optimizing Tailwind CSS builds in local development. It explains how splitting CSS imports can avoid reprocessing the full Tailwind utilities stylesheet during ordinary CSS changes, improving Hot Module Replacement and Live Reload responsiveness. ### Source excerpt Learn how to optimize your Tailwind CSS PostCSS build times to make local development with Hot Module Replacement or Live Reload orders of magnitude faster! ## Setting Up Live-Reloading ClojureScript Development with Boot DevFeed: [Setting Up Live-Reloading ClojureScript Development with Boot]() Original publisher: [Read original article]() Published: 2016-01-11T00:00:00Z Content type: tutorial Language: en Sources: [Adam Bard]() Topics: [ClojureScript](), [boot](), [configuration](), [Development](), [Documentation]() Tags: [boot](), [configuration](), [dependencies](), [development](), [reload](), [repl](), [vim]() ### AI overview A tutorial for assembling a live-reloading, auto-compiling ClojureScript development setup with Boot. It explains the required dependencies, configuration, and task composition, including starting a REPL and passing the fileset. ### Source excerpt My long-standing complaint about Clojurescript is that it's a pain to get running. People who prefer Leiningen seem to have gotten a handle on this with figwheel; however, those of us who have jumped on the Boot train (it's newer and therefore better!) still have to do some assembly to get the live-reloading auto-compiling repl setup that's become the standard for Clojurescript development. Like many problems in the Clojure universe, this is less a problem of technology and more a problem of approachable documentation. With just a little bit of configuration and some understanding, you too can assemble that perfect Clojurescript dev setup using Boot. ## The Refresh Test DevFeed: [The Refresh Test]() Original publisher: [Read original article]() Published: 2014-04-10T00:00:00Z Content type: opinion Language: en Sources: [Robin Ward]() Topics: [Ember](), [Website](), [browser](), [App]() Tags: [app](), [browser](), [ember](), [fields](), [form](), [make](), [reload](), [required]() ### AI overview The article argues that web applications should preserve form data and tolerate page refreshes. It uses frustrating account-creation and online checkout experiences to illustrate the problem, then discusses how Ember App Kit's live reloading encouraged the author to make an application refresh-resistant. ### Source excerpt How many times has the following happened to you? You go to a web site and it asks you to create an account. You fill out a form with all the obvious fields and hit submit. The page refreshes and shows you the form again. Phone Number is required Well, that's annoying. There was no indication that the site needed your phone number. You prefer not to give out your phone number to every web site, but this one is run by a company you trust, so you scroll down and fill it out. You submit the form again.