This question is often asked, but is never answered properly. So how to measure framework speed? Let me also explain why "scalability" is more important than general "performance". [...] This along with a general overheads of the framework greatly contributes to the "slowness" of your project. So how can framework contribute to performance of your project?

They touch a few different ways that frameworks can help execute things a bit faster like:

• Make Fewer SQL Queries
• Selective render
• Parallelization
• Overheads
• Caching

Today - any desktop software is able to re-draw itself from a callback by operating system. However many Web Frameworks today do not keep track of objects and cannot selectively produce pieces of HTML code. I believe that ability to have control over objects on HTML pages is very essential to have in the Framework. Here is why...

He starts with a look at how desktop software handles things, then moves to the state of web rendering ("still in the 90-ties"). He talks about their better approach to things - creating a two-pass walkthrough where rendering is done on each of the objects in the page first and then those are passed to a "master parser" for overall display. A simple PHP code example is included. Creating an application with this approach makes performance, javascript integration and other templating features simpler.