scotty VS htmx

I would suggest checking out scotty for the http server - it uses warp by default, and is very beginner-friendly.

Here's the current commit I'm working with: https://github.com/scotty-web/scotty/commit/3ed8586c046b46dc42740e8ac2e7fe712e84191d

If you're not a fan of the ruby-on-rails / swiss army knife approach that IHP takes, check out Scotty. Add Lucid for Html rendering, and Selda for Postgres. (There are other options for any of these tools if you prefer)

- Scotty (simple web routing) https://hackage.haskell.org/package/scotty

Writing a Haskell webserver (maybe using scotty) and call it from node.

I've been looking for this as well, and found the globalstate.hs example in the scotty github repository. It uses a ReaderT of a TVar and shows how to update or read shared state in memory.

I've found htmx and hyperscript talking to scotty to be an easy way to get something like this going while retaining the joys of Haskell on the backend and avoiding the pains of Haskell on the frontend.

Finally, to add my opinion in the context of some other posts: I'd suggest Scotty (and probably other libraries I'm less familiar with) before Servant in particular, as Servant is a lot to absorb if you're also trying to build fluency in Haskell at the same time. Similarly, I'd advocate for Elmish (disclaimer, it's written by (very talented programmers other than myself at) my company) over Halogen, at least based on the last time I tried Halogen--I found it pretty complex as well. Don't get me wrong, I think Servant and Halogen are both great, just...complex.

This is an example of REST API built with Scotty a web framework of Haskell and PostgreSQL a relational database. It's a simple API to manage products.

Not that I'm much of an expert, but if you're talking about a very barebones static single-page-app, then you could very easily get by just using blaze-html to put your elements on the page, and then scotty is a basic web framework you could use to serve up your app.

Recently, I just rewrite one of my application Stashbin from Next.js to GO. Though my main motivation of this migration was to learn GO and experimenting with HTMX. I also aiming to reduce the resource usage of my application and simplify the deployment process. Initially, Stashbin codebase are split into two seperate repository, one for the frontend that uses Next.js and another for the backend that already uses GO. The backend repository is just a REST API responsible for storing and retreiving data from the database.

HTMX is another library that gained popularity due to its server-first approach to rendering data, although seeking a much simpler way of appealing to developers.

When I work with HTMX I need isolated component that can be reusable a form. So I create a PHP Function that generate the Input Datalist.

I was inspired by htmz (which was in turn inspired by htmx) and how the author got pretty close to a basic htmx-like experience just using an iframe. I wanted to push it a little further so whipped this demo together. My submission demonstrates progressive enhancement for the form - with js enabled the request targets an iframe that is inserted into the dom, meaning the page doesn't actually navigate (similar to event.preventDefault()). The iframe receives the html response from the request and on load triggers a function to swap out it's contents into the main page.

As described on htmx.org: "htmx gives you access to AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML, using attributes, so you can build modern user interfaces with the simplicity and power of hypertext"

Apart from the source code itself, the repo's README also gives a bit more details about the various packages I used.

1. htmx: https://htmx.org/

Also, there’s some response header juggling you have to do when submitting forms that have a validation step before redirecting: https://github.com/bigskysoftware/htmx/issues/369

I’ve tried to iron out any footguns or server requirements I’ve bumped into while using HTMX & Hotwire in my projects.

✨ In recent months, I have been developing web projects using GOTTHA stack: Go + Templ + Tailwind CSS + htmx + Alpine.js. As soon as I'm ready to talk about all the subtleties and pitfalls, I'll post it on my social networks.

I've been digging into HTMX lately (using Python web frameworks) and find the concepts and approach to be interesting and promising. The idea of hypermedia driven systems over the current practice of JavaScript based frameworks (I never really got into React, played with Vue, and enjoy Svelte/SvelteKit) and the ability to chose your language/framework for the backend while primarily leveraging HTML/CSS on the frontend just seems refreshing.