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

But the great benefit of returning to Server Side Rendering (SSR) is not needing APIs. Creating an API, whether REST or GraphQL, makes development slower. And it's not just Rails that is realizing this; Elixir with Liveview, PHP with Livewire, and even JS with HTMX, and React are following this trend. As Deno.js says: The Future (and the Past) of the Web is Server Side Rendering.

I also needed to keep the infinite scroll on the homepage, authors, and categories pages which allow for scrolling all 200 posts as paginated pages of about 10 posts. To do so, I used partial HTML render routes that I render at build time with Astro (like any other page) and used HTMX to fetch pages on scroll. You can try it by scrolling on the blog homepage to see requests going out when scrolling to load the next page and inject it into the current document.

I expect the author would mostly agree with you, but see the "motivation" header under https://htmx.org/

A way less marketed version of this is htmx [1]. It is a single javascript file that enables this functionality. I mostly see people using it with Go backends but I think it is flexible. I have been meaning to try it out for a year or so.

1. https://htmx.org/

Since its first release in 2020, htmx has grown in popularity to over 30k stars on GitHub, which looks promising. However, it has yet to dethrone React, which boasts over 220k stars on GitHub.

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.