sprig
quicktemplate
Our great sponsors
sprig | quicktemplate | |
---|---|---|
11 | 12 | |
3,985 | 3,003 | |
1.8% | - | |
0.0 | 0.0 | |
2 months ago | 10 months ago | |
Go | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sprig
-
Templ: A language for writing HTML user interfaces in Go
Standard Go templating seems really lacking if you come from something like Jinja. Even with libraries like https://masterminds.github.io/sprig/ (used e.g. for Helm templating) it feels hard to use.
-
Improve performance of Go serving a React frontend
Eleven, you'd be surprised what go template libs are out there like sprig. https://masterminds.github.io/sprig/
-
What would you choose if you are in my shoes?
If you use Go templates be sure to use Sprig as well to get more usable functions.
-
Library to convert HTML to pdf in Golang
I'd highly recommend tossing in the sprig library and depending on how you break up your templates, maybe creating a custom "include" helper instead of using the built in define/template helpers. The advantage of this is that if each template is capable of rendering itself independently, you can potentially render all of your templates in parallel.
-
Jsonnet – The Data Templating Language
The discoverability of golang templates is terrible, IMHO, since it's missing a "dir(locals())" equivalent and every execution environment gets to make its own rules about what pipelines/functions are exposed
Look at helm as an example: https://helm.sh/docs/chart_template_guide/function_list/ is some of them, https://helm.sh/docs/chart_template_guide/accessing_files/#p... are some others, but they also glued in some version of https://masterminds.github.io/sprig/ So, short of (a) knowing that's the case (b) having 3+ bookmarks in your favorite browser to refer to those reference pages, how would anyone know what pipelines are available?
Separately, I dooooo nooooooot understand why every joker has to invent their own new thing when we have like 50 or so templating languages already. Golang may be an outlier in that competition due to the Google Promotion Packet Effect(tm) but how they came up with `{{ range }}{{ end }}` as sane syntax is some true facepalm, to say nothing of the same landmine that ansible stepped on by not switching jinja2's default characters: `{{` is not _yaml safe_
-
Charm: a new language in, with, and for Go
You mentioned something about PHP. We also already have a templating language in the standard library that can be extended (commonly done with sprig).
-
Is there something similar to plopjs in Go? (generate files based on configuration from templates)
Plopjs looks interesting and is probably not too hard to write for yourself in Go. You could add something like sprig for some useful template functions.
-
Tips for running "good" coding interviews?
Not at all. It was "write a helm template using the following imaginary values in a values file". In 30 minutes, I was able to google the Kubernetes api and the sprig functions for templating, complete the assignment, fix a stupid typo the unit test caught, and spend 5 minutes trying to think of any corner cases that hidden unit tests might catch (I don't know if there were any hidden unit tests). The goal of this take-home assessment was to prove that you are not wasting an engineer's time when they call you, not to prove that you should be hired.
-
tfcmt - Improve Terraform Workflow with PR Comment and Label
Support sprig in Template
-
Kyoto – Build Front End with Golang
They may refer to the definitive shortage of built-in functions. The template engine itself only provides the bare minimum. That's usually not a problem because of template function libraries like https://github.com/Masterminds/sprig
quicktemplate
-
Templ: A language for writing HTML user interfaces in Go
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
-
Full stack web dev with Go.
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.
-
What is the current ideal choice for server-side rendered web frameworks?
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
-
The templ templating language: 2 years later
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
-
Go Time #266: Is htmx the way to Go?
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...
- Ask HN: Slimvoice Alternative?
-
Using multiple repositories in your CI builds
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,
-
Why Hugo’s Documentation Sucks
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?
-
[HELP]XML encoding and decoding
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.
-
Templ - a new templating language for Go, with autocomplete, syntax highlighting and formatting
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.
What are some alternatives?
pongo2 - Django-syntax like template-engine for Go
Jet Template Engine for GO - Jet template engine
liquid - A Liquid template engine in Go
hero - A handy, fast and powerful go template engine.
Plush - The powerful template system that Go needs
fasttemplate - Simple and fast template engine for Go
goview - Goview is a lightweight, minimalist and idiomatic template library based on golang html/template for building Go web application.
amber - Amber is an elegant templating engine for Go Programming Language, inspired from HAML and Jade
gofpdf