<div><span class="gmail_quote">On 1/31/06, <b class="gmail_sendername">Robert Brewer</b> <<a href="mailto:fumanchu@amor.org">fumanchu@amor.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>That's true, but I'd caution that "it's just something you use" hides a<br>mountain of difficulties. A standard like WSGI can be relatively free in
<br>its interface design (in order to meet a host of specialized needs),<br>because it has a limited user group. A template standard, in contrast,<br>will need much more attention paid to "ease of use", which will
<br>constrain its interface design.</blockquote>
<div> </div>
<div>The user group of a standardized template API would be a framework author. Different frameworks would still access their templating engines in different ways, but with a standardized template engine API, you'd be able to plug different templating engines (
i.e. django, cheetah, kid, zpt, psp) into different frameworks, and have it Just Work.</div><br>Peter Hunt</div>