To be fair, Django doesn't make you adhere to that pattern and you can use Django any way you please. Django has a lot more "in the box" than Flask and I will agree that I think it's more difficult to get started with.
Not to mention that Django is a framework and WordPress is an application. It's like comparing a box of Legos with a box of unmolded plastic and then declaring that the former is easier to play with.
To continue with the analogy one might say that Django comes with the molds but you have to know how to use the furnace and how to make the bricks without them turning out crappy. Much greater potential because you can make whatever you want but also higher barriers to entry.
Yea you are correct. Just saying when you read a Django tutorial and they say a "View is not a View", meaning that the Django View is different... that is not exactly newbie friendly.
I'm not so sure, I understand Model-View-Template much better than I understand Model-View-Controller.
And for a real beginner, what a view is doesn't matter at all; what matters is how quickly they can start to feel they understand what they are doing with the system.
So your argument from personal knowledge is why something is easier or harder :)
Here's my experience: Having attempted to do semi-meaningful things in both a few years ago, I can tell you that hacking on wordpress and figuring out its internals (as a newbie in php) vs hacking in django (as a newbie in python) that the django experience was orders of magnitude more effort.
To be fair to Django, their concept of View is closer to what it meant originally, before MVC was adapted by Rails et all. And if you're a complete newbie, you don't have any preconceptions of View anyway. It's only a problem if you come from other Web frameworks.
