Configurable templating engine

[pedromss]

I've been playing around with oto and one of the first things I wondered was why would the templates not be written in the text/template or the html/template?

And with that in mind I was thinking if a feature like a configurable templating engine would be interesting from your point of view.

The benefit is that new comers to oto, who don't know plush (like me), don't have to go and learn a new templating language. There's another, more subjective thing that could be considered: "if the standard lib has what I need, why go to a third party alternative".

The interface for the command line could be a new optional parameter --engine {text/template|html/template[|plush]}. The absence would mean the plush engine and that would preserve compatibility.

---

I've glanced at plush but at first sight couldn't see the need for it over the std lib (could be an historical thing, like at some point in the past the Go templating engines weren't enough), so if its something obvious I'd love to understand, should you know it.