pagoda VS Alpine.js

Recently, I have stumbled across this one: https://github.com/mikestefanello/pagoda

I'd like to make a small plug for a really awesome Golang web development starter kit I found recently called pagoda (https://github.com/mikestefanello/pagoda). It wires up HTMX, together with Alpine.js and Bulma CSS, onto a really fantastic collection of Go libraries on the back end.

Well said. The 'no big framework' thing works for Go because the Go standard library defines a common way for dealing with HTTP. The difficulty, then, is identifying 3rd party packages that play well with the rest of the ecosystem.

You can see the opposite in projects like Echo, Gin, Beego, etc., that eschew the standard library to various degrees and try to build the kitchen sink themselves. Sometimes this works! Echo is very popular, despite having nonstandard handlers and context. An absolute Go newbie is probably going to have an easier time using it than trying to pick out the best collection of libraries themselves.

I would love to see more 'blessed stack' collections that tie together good libraries such as this one: https://github.com/mikestefanello/pagoda

The readme doesn't seem to mention or list what libraries this depends on, it has chi and jet at least based on the structs section.

Given this "framework" is predominantly a collection of other people's (usually apache/mit) work, where is the BOM/licence text including all of the dependencies?

And why has the author attempted to licence their likely sub 100 lines of glue code under the GPL?

I don't see the point in using something like this which is basically a prefilled go.mod with some other files with a pretty stock organization.

I've used Pagoda (https://github.com/mikestefanello/pagoda) in the past which makes a show of displaying its nature as a wrapper around a bunch of community libraries, and is documented as such. They also make effort to document the interfaces for each component so you could easily replace them with your own implementations to avoid getting stuck due to the "framework". This is my preferred approach for all of these "starters" now since using pagoda.

I recently came across https://github.com/mikestefanello/pagoda - which is also a very good starter kit. Unfortunately it comes with some tools I personally don't like a lot (yet) - like htmlx for templates. I suppose this is a problem of all starters - you can only build one which is ideal for you, but not for others. But anyway it's simpler to remove/replace unnecessary parts than create everything from scratch.

Pagoda looks really nice

You may be interested in pagoda (I'm the author) which is a starter-kit for rapid, easy full-stack web development in Go, built upon Echo (web framework) and Ent (ORM). It should give you pretty much everything you'd need right out of the box.

Alpine.js for reactive frontend

✨ 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.

> But honestly, torn towards htmx but undecided.

We are in the middle of migrating from our monster react application into server rendered pages (with jinja2). The velocity at which we are able to ship and the reduction of complexity has been great so far.

Managing client side state for simple things like (is the dropdown open/closed), listening to keyboard events and such can be done with something like alpine-js [1] without all the baggage that something like react brings.

It appears this is already the trend with JS frameworks too - with server side rendering being the new norm.

[1] https://alpinejs.dev/

Sure, you can use any number of JS-avoidance libraries. I'm a fan of Turbo, and there's also htmx, Unpoly, Alpine, hyperscript, swup, barba.js, and probably others.

If you want more details on the initial setup I encourage you to take a look at the Part I that covers more of the initial implementation. For this portion, I added Prisma as an ORM, a frontend style library called Tachyons, and AlpineJS to handle any client-side interactions. I did this to avoid needing to add a client-side bundler to the build and instead just rely on plain old module imports to compose the frontend. This is now the default for Rails and it is quite nice to not need any additional build tools for the client.

- [swallow-pywebview](https://github.com/rangwea/swallow-pywebview)： Base on [pywebview](https://pywebview.flowrl.com/) using Python，the frontend base on [alpinejs](https://alpinejs.dev/) and [tailwindcss](https://tailwindcss.com/)。

The approach is not new, essentially a variation of Knockout, Alpine, and similar "JS-in-HTML" approaches.

alpinejs + htmx

You're way out of the "simple website" territory already, If your backend is working and you know your way around it just make it render some HTML and send it to the browser. Then if you really want a javascript framework for interactive elements maybe alpineJS ?