Skip to main content

Benchmarking HAML vs JADE vs HTML in PHP?


I'm interested in the performance of templating languages in PHP. I've been watching node.js tutorials and am really impressed by the use of JADE (http://jade-lang.com).



I see that JADE can be used in PHP https://github.com/everzet/jade.php and am wonderring about how it works in terms of performance.



I gather that when running for Node or Ruby the HAML or JADE is compiled when the server is started, but since (I gather) PHP loads at request-time there may be performance implications when using a templating language in PHP (then again, maybe the templates are compiled and stored in the cache).



Has anyone seen or done benchmarks of how PHP performs when using HAML, JADE, (other template languages that I don't know about) versus writing the full HTML ? What other considerations should I be aware of? (Assuming an MVC style framework)


Source: Tips4allCCNA FINAL EXAM

Comments

  1. I just implemented Jade.php for one of my Zend Framework projects.

    They do cache the parsed jade files as php files, and just include them at runtime. That's what the Zend Framework does with the phtml files, i.e.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex