I made webdev in several languages and frameworks, including python, php and perl. I accept them myself, and my largest sites receive about 20 thousand hits per day.
Any language and framework that has a reasonable speed can be increased to 20 thousand hits per day, just throwing resources on it. Some take more resources than others. (Plone, Joomla. I look at you).
My witty sites (not yet made) take up a lot more (from memory by about 5000%), knocking (using seige) than, for example, my python sites. I.e. When I hit them as hard as I can with seige, witty sites serve a lot more pages per second.
I know this is not a real general test.
Other speed advantages that wittily give you:
Multithreading
If you deploy with a built-in websrever (for example, behind a ha-proxy) and your application is multithreaded, it will load a lot less memory than saying a perl or php application.
Typically, with php and perl applications, you will run Apache for each incoming connection, and each process loads the entire PHP interpreter, all the code, variables and objects, and what not. With heavy frameworks such as Joomla and Wordpress (depending on the number of plugins), each process can receive supernatural memory consumption.
In a Wt application, each session loads a WApplication instance (C ++ object) and the entire widget tree and more. But the memory that the code uses remains unchanged, no matter how many connections.
Embedded Web2.0 ness
Typically, with traditional applications, they are still built around the old "HTTP request". "We serve the page" .. "done" style of things. I know that they add more and more AJAXy ticks all the time.
With Wt, it by default uses WebSockets, where possible, only to refresh the part of the page that needs updating. It returns to standard AJAX, and then if it does not support HTTP requests. With clients that support AJAX and WebSockets, the same WApplication C ++ object is constantly used. Therefore, when setting up a new session and speed, the speed is not lost.
In response to "C ++ is too complicated for webdev"
C ++ has a bit of a learning curve. In the mid-nineties, we made websites in Java j2ee. It was considered commercially viable at the time, and it was a great frightening pain to develop, but it had a good advantage in promoting good documentation and coding techniques.
Scripting websites make it easy to use shortcuts and not realize that they are there. For example, one 8-year-old perl site I was working on had some code duplicated and no one noticed. Each time he showed a list of products, he ran the same SQL query twice.
With a C ++ site, I think it would have less chance because the Perl site did not have such a programming structure (as functions), it was just perl and built-in html. In C ++, you are likely to have methods with names, and ultimately with name collisions.
Types
Once there was a method that accepted the identifier int, later we changed it to the string uuid. The Python code was great, we didn’t think we needed to change it; he went perfectly. However, there was a small line deep in the depths, which had a different effect when you passed the line to it. It is very difficult to track down the error by messing up the database. (Fortunately only on dev and test machines).
C ++ would probably complain a lot and make us rewrite the functions involved, rather than being lazy buggers.
With C ++ and Java, compiler errors and warns of many such errors for you.
I believe that unit testing is usually not so necessary with C ++ applications (don't shoot at me), compared to applications in the scripting language. This is because the language provides many things that you usually add to the unit test for a python application.
Summary
From my experience so far .. Wt takes more time to develop material than existing frameworks .. mainly because existing frameworks have much more features. However, it is easier to make extremely customized applications in Wt than Wordpress imho.