bau VS htmx

Likewise, done with React. I wrote Bau, an alternative to React in less than 300 lines of code, as well as a css-in-js lib (bau-css), a router (bau-router), and a component library (bau-ui). Check it out at https://github.com/grucloud/bau

Check out my reactive ui library called bau, under 2kB, 25 times leaner than react. The philosophy is simple: easy to use and hard to misuse. There is no JSX, no Virtual Dom, no api that requires reading a long guide on how to not misuse it (useEffect can you hear me?). On top of it, there are libs to perform css in js, routers, multi-page app, components library, etc.. Available at https://github.com/grucloud/bau, feedback welcome.

I built a css-in-js library under 33 lines of code: bau-css, 25 times smaller than styled-component, it is also much faster as no CSS parsing into an AST is performed. This is accomplished by using the css nested feature of modern browser.

Check it out at https://github.com/grucloud/bau/tree/main/bau-css

I'm stoked to announce the release of bau-css, a lean CSS in JS library that simplifies your styling needs. It's just 33 lines of code and offers an API compatible with styled-component emotion. Check it out here: https://github.com/grucloud/bau/tree/main/bau-css

Thanks, I've just added mine called bau, a reactive ui library under 300 lines of code, available at https://github.com/grucloud/bau

Hi there! I want to show off a little feature I made using hanami, htmx and a little bit of redis + sidekiq.

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.