Hacker News Reader

Comment by rampage101 | Hacker News Reader

The difference in difficulty between Python/Django and WordPress is massive.

To do Django you have to know Python, which is a big assumption. For Wordpress you need basically zero programming knowledge.

Also compared to Flask, Django is much more complicated by making you adhere to their MVT (Model-View-Template).

View on HN

I wouldn't agree with any of that, especially not the first part!

We even have a tutorial series especially aimed at non-Python programmers: https://www.django-cms.org/en/blog/2016/02/16/build-a-websit...

The trickier part is deployment, which is where WordPress (all PHP, really) truly shines for ease-of-use - and this is where our Docker-based Aldryn Cloud platform intends to bridge the gap, by making that just as easy for Python/Django users.

I hate to be 'that' guy, but... py2.7? :( Come on guys, get it on with py3!

It works with Python 3 too!

Ah, ok, sorry. The tutorial confused me there for a sec: https://i.imgur.com/0Zyygrs.png

At work I'm running django-cms on Python 3.5. But not on the specific platform setup that tutorial is for :)

Shouldn't you compare Django CMS to Wordpress, not pure Django? If you want to do code changes in Wordpress, you need to understand PHP + Wordpress conventions as well.

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.

If they are a beginner it probably doesn't matter.

They're talking about Django CMS, not the framework. It's a CMS just like WordPress. You don't have to know programming if all you need is a simple page, a blog, or the likes.

I missed that somehow haha... thanks

PHP/Wordpress are ok if you're willing to cut corners.

I'm not being sarcastic, everything is a tradeoff, usually you have to cut corners somewhere.

Reply on news.ycombinator.com