Buffalo VS pagoda

You should probably stop because this is not a Go-way. And you wan't find anything with "batteries" other than https://github.com/gobuffalo/buffalo and https://github.com/beego/beego

Haven't see anyone actually using them in production though.

No default. There is Buffalo which is modeled after Rails, haven't used it in anger though.

https://gobuffalo.io

In general, no. But if you do seek for one, I think https://gobuffalo.io is very good.

There is https://gobuffalo.io/ and there is https://github.com/livebud/bud. Both are interesting approaches, but sadly, without real business interest from the community. See, 90% of what makes Laravel Laravel (or Rails Rails) is business adoption. And, as you will sadly find out, the business adoption for traditional Web applications is exactly zero. If you don't want to make the same mistake as I did, and spend 3 years of your life searching for it, do as the others advised - just use the tools and frameworks that have already been built to solve the problem you need.

If you like Ruby on Rails, there is Buffalo.

Buffalo is currently built on Gorilla which complicates building a business on it right now as Gorilla has shifted to public archive since it has no maintainer. https://github.com/gobuffalo/buffalo/issues/2360

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