Evaluating template engine to use

[endorama]

This tool currently uses 2 different template engines:

• placeholder, a custom, in house developed template
• gotext, the Golang text/template package

In PR #40 we evaluated different template engines: placeholder, jetHTML, hero, text/template. (results available in the linked PR)

We decided to move forward with 2 template engines:

• placeholder allows for unmatched performances, as it does not provide any control flow operation
• gotext is the second most (non precompiled) performant and maintained template engine available from this benchmark

jetHTML has been discarded as the version with high performance from the benchmark was an older and unmaintained version. hero has been discarded due to the complexity of using it with dynamic templates. More details in the Outcome section of the linked PR.

Thanks to how the different templates are implemented, adding additional templates is possible.

[endorama]

As Elastic product use Mustache template engine, which we may consider to use to provide consistency.

Is to be noted that from the benchmark Mustache provides half the performances of text/template on CPU and is 13x less performant memory wise.

We may want to re-evaluate the benchmark for our use case to provide more appropriate data.