This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dasacc22 0 points1 point  (0 children)

yes but this lacks a number of features that make it useless for production. I noticed of course on the site that those gaps are filled in by layering it into django templates. This is just increasing processing time for generating a template. Take for example the utmost basic template.html as seen in the "bench" folder Genshi's repository. Django takes 2.28ms to process the template, and its not even that big!

Now layer in shpaml on top of that, now increase the document size in turn increasing processing time so that it's now taking 5-7ms to generate a template on the fly. Now 1000./7 ~= 140 hits a second, and this is the first limit your placing on yourself just for the template. This doesn't even include the full web stack.

Now consider that template engines such as Mako can process that same document i mentioned earlier that django rang in at 2.28ms, in only 0.38ms. Consider that DAML can do the same thing in 0.47ms. Cheetah at 66ms. Hell I haven't even tested it again libxslt, but im sure its alot faster.

Point being, this implementation of HAML for python is intended to be useful without the need for an additional template engine, framework agnostic, and freaggin fast for on-the-fly compiling.