I bought agile web development with Rails 2 years back(appx) after hearing all hoopla about Rails. The quality of the book was comparable the Pylons online documentation (which has taken some interesting bits from Rails).
The django documentation has been consistently superior from day one. Its the only documentation I refer to when developing with Django. I may dive into the source code to better understand things infrequently.
The other documentation artifacts, like slides, produced by Django core developers are excellent enough to be reused in teaching django.
So, if the blog's author is trying to use no of books as a metric to prove anything, it may be something to do with the gullibility of the target audience and/or lack of solid documentation on the framework website.
The django documentation has been consistently superior from day one. Its the only documentation I refer to when developing with Django. I may dive into the source code to better understand things infrequently.
The other documentation artifacts, like slides, produced by Django core developers are excellent enough to be reused in teaching django.
So, if the blog's author is trying to use no of books as a metric to prove anything, it may be something to do with the gullibility of the target audience and/or lack of solid documentation on the framework website.