You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API is ridiculous. You have to parse each template (and that may fail) and then you have to ‘execute’ it (and that may fail too). Simply unbearable
If we use html/template, it will be easier to implement template configuration, which is undesirable
Pro:
It is in stdlib
If we store the templates as separate .html files, every text editor will have a proper syntax highlighting. Compare with .qtpl which requires additional configuration everywhere
So, what is better? Cross your sword!
The text was updated successfully, but these errors were encountered:
We use the quicktemplate library for almost all of HTML templating tasks in the project.
Contra:
.qtpl
and.qtpl.go
)Pro:
I do not think changing quicktemplate to any other non-stdlib templating solution is a good idea. But what about stdlib's html/template?
=> https://godocs.io/html/template
Contra:
Pro:
.html
files, every text editor will have a proper syntax highlighting. Compare with.qtpl
which requires additional configuration everywhereSo, what is better? Cross your sword!
The text was updated successfully, but these errors were encountered: