quicktemplate VS Buffalo

Here are a couple:

https://github.com/julvo/htmlgo

https://github.com/rohanthewiz/element

I'm sure there are many more.

The thing about these is that performance is often not as good as when using templates, especially when the templates are compiled to native code. Quicktemplate [1] is still the leader here IMO, and I don't think the OP project brings much that couldn't be done pretty easily with QT.

[1] https://github.com/valyala/quicktemplate

From my experience you don't really need a distinct frontend framework for web development in Go. I've been able to use quicktemplate for some of my projects for rendering HTML pretty effectively. I've written about using it here.

If the question is about templating libraries, then I've seen people use other libraries than the html/template, like https://github.com/hoisie/mustache or https://github.com/valyala/quicktemplate

I originally started out trying to add features to quicktemplate, but didn't get any engagement, so went my own way: https://github.com/valyala/quicktemplate/issues/80

I've been using quick template with htmx and I'm really enjoying the combo. As a mostly backend developer it's a pretty intuitive approach. Now if someone could just build something to simplify working with CSS...

Like with the previous post, we're going to use djinn-ci/imgsrv as an example of using multiple sources in a build manifest. If we look at the top of the manifest file, we will see that it requires three repositories to build. These are, the source code for djinn-ci/imgsrv itself, golang/tools, and valyala/quicktemplate, defined like so,

I like Hugo quite a lot, but I don't like Go's standard library templates. I wonder if it is possible to use https://github.com/valyala/quicktemplate with Hugo?

For encoding, the receivers usually want very specific encoding (namespaces, nil as xsi:nil, not omitted value...) - templating with text/template or github.com/valyala/quicktemplate is easier on the long run, than fight with xml.Marshal and the other end's unspoken assumptions.

The "Hello World" example is up at https://github.com/a-h/qt-lsp - it's called qt-lsp because I started down this track looking to build IDE support for quicktemplate - https://github.com/valyala/quicktemplate/issues/80 - but didn't think it was practical when I dug into the design of quicktemplate more.

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