> > Should we forfeit these checks because others do not do them and we want > to appear faster in the benchmarks? I say no. >
+1 I completely agree with this. After some months working with another framework I say that the speed issues is not a problem compared to the hard way of getting things done. With the fine-tuned uwsgi+nginx I have all the web2py advantages and also the speed because uwsgi is taking care to respawn my problematic workers, that is seamless to my users and the app works very well. "Premature optimization is the root of all evil!" I recently understood this sentence, I tried to have a "performatic" app and I've lost more time on this than on my app core. At the end I solved performance issue on the server deployment + web2py best practices as the use of cache, session.forget, migrate=False and wise use of models. --
