template VS statigz

Out of the box, Go Fiber already has mechanisms that will allow us to add some frontend views to our app. We will need to use a template engine. Go Fiber supports several template engines. The full list of supported template engines can be found on their website. For this tutorial, we’re going to use the html template engine.

Check out the go.mod file of the fiber templates package and inspect the ones that look nice to you - https://github.com/gofiber/template

Their rendering handling seems to be a lot better than gofiber's[1] which downloads nearly 1,000 packages and sadly ruled it out as a viable framework when I was looking for web frameworks to use.

[1] https://github.com/gofiber/template/blob/master/go.sum

The Fiber team supports template package that provides wrappers for multiple template engines:

I've made an http file server to serve pre-compressed or decompressed files out of embedded fs based on Accept-Encoding header: https://github.com/vearutop/statigz.

I thought this approach can work well for Go embedded files too and implemented github.com/vearutop/statigz: a file server that can serve compressed version of an asset if it is available in embedded file system.

I'm excited with this new feature, though I felt a bit of friction in the case of serving compressed assets with http. I like how such problem in solved in http://nginx.org/en/docs/http/ngx_http_gzip_static_module.html, so I've implemented somewhat similar approach for Go 1.16 embedded files: https://github.com/vearutop/statigz, hope it will be helpful.