I don't understand where he gets this idea that Django uses an ActionController kind of object. Django provides the facility for you to write a class-based view

I don't understand where he gets this idea that Django uses an ActionController kind of object. Django provides the facility for you to write a class-based view if you want, but it does not require one. In fact, the only promise Django makes (known as "The Django Contract") is that, given a callable as the endpoint to one of the routes in the urls.py file, it'll execute that callable with the request information and forward whatever you return from that callable as the response to the client. Just based on that I have to take the article with a rather chunky grain of salt; let alone the grandiose statement at the end saying that their framework is the only one that "gets it right". I don't mind the link-baiting to sell your own fish every now and then, but attitudes like the one displayed by the author are definitely not selling me into trying their software.