You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') AND date > NOW() - INTERVAL 1 WEEK ORDER BY views DESC LIMIT 0 , 10' at line 1
I was not talking about retyping the new password, but about requesting the old password before you can change it. The reason you do this is because even if you theoretically could hijack the session, you still can not hijack the account. But the priority seems a bit off when the password is more important then the account, which makes you believe that the people behind the sites only added the extra password validation because they seen it every where else, and not because they understand the principle behind it.
It's like all these sites that requires you to enter your current password before you can change it, but deleting the entire account is just ticking a check box (at least twitter and dribbble worked this way back when I had accounts there).
Some things we been doing for so long that we forget why we do them at all.
Isn’t it that django and rails has flat curves because they are by nature blocking. So it wouldn’t matter how many request you throw at them as they are limited in how much they can handle at once.
And to on top of this compare database requests is meaningless as the blocking nature of the framework itself is the major bottleneck, and not the database.
Now, for a normal web application, the largest amount of request would come from static content, or cached content within the web app so the real gain would be a tiny fraction between python/ruby and go/java-based frameworks.
That said, if you want to handle static content (images and such) from within your app, or build a java script-centric application with lots of tiny requests, or even persistent once...nor rails or django would do.