kotlin-flow-extensions VS htmx

I don't know, why I'm downvoted here, but it is very relevant if the library provide the operators you need or if you have to implement them yourself. If Kotlin Flow is enough, then use it. From experience you don't have to go to far to miss operators from Reactor or RxJava. Maybe some day additional libraries like https://github.com/akarnokd/kotlin-flow-extensions will fill the gap, but for the time being Reactor or RxJava offer a lot more for (not trivial) real world use cases.

Why do you want to keep Flow such a small library? It could be an attractive alternative to RxJava or Reactor, but it misses many useful operators today. On the other hand it brings a lot more operatores than would be required as a foundation for other frameworks (likeKotlin Flow Extensions). From my point of view Flow stays in the middleground with no good reason.

⚡ HTMX → https://htmx.org

SOME of you may know by now that I'm a fan of htmx and its hypermedia-driven website/application design philosophy. When people first learn about htmx, they are often captivated by the idea of hx-get, hx-post, hx-delete, etc. attributes being able to fire off HTTP requests with these methods from any tag on the page. I know I was!

Today, we will be replacing HTMX in the project with HMPL.

🔗 Here’s a 2-min intro to HTMX that will blow your mind: Why HTMX is the Future of Front-End

HTMX on GitHub

But I want to say that this topic is clearly not new in 2025, I will not reveal anything supernatural here. HTMX and Alpine.js have already fully proven to everyone that this is not nonsense. I am just retelling everything, but with one interesting remark - this is the HMPL template language which is better than the previous two in some tasks. Next, I will describe why and how it will help you replace Next.js.

At the forefront of this hybrid model stands htmx, a pioneering framework that champions a simplified approach to dynamic web development. By leveraging data attributes, htmx grants developers the ability to control client-side interactions directly from the HTML markup. This means that the primary focus shifts back to generating valid HTML on the server, while htmx seamlessly inserts and updates this content within the DOM as needed. Consequently, developers can maintain a clean and straightforward server-side codebase while still delivering interactive and responsive user experiences on the client side.