Django vs Pligg - which tool is easier and faster?

Question

Django

What to choose, Django or Pligg for such a (similar) site www.voat.co ?
And most importantly, why?

Answer 1

Pligg is a big noname of dubious quality of implementation and content.
If you want PHP - go towards Symfony2 + Sonata and other bundles, cut according to your needs.
"Easier" - almost everything is equally "complex", and there is nothing more complicated than MVC + 5th or 6th normal form of the database.
I don't like Django because of the rather large number of dubious crafts, I often look towards Pyramid + SQLAlchemy.
"Faster" - I would say that neither puff nor python is particularly "intelligent and quick-witted", although IMHO PHP 5.6 works faster than CPython and a little slower than PyPy.
If you need "faster", dozens of times, it's better to go to Java + Netty like Vert.x or Play2, you can use golang.
If some kind of reactivity with rich frontends and all sorts of Flux / CQRS-ES etc is not planned for updating content via Websocket / SSE / longpolling etc - in most cases it is enough to implement normal second-level caching, taking into account the relational model. Here with PHP / Python / Ruby for such tasks of push notifications, you need to turn gearmand / celery / sidekiq - because there is no normal multithreading out of the box.

Answer 2

If I understand correctly, the question is about the implementation of the voting system.
There are (almost) ready-made solutions for Django, including:
As for the CMS itself, there are a bunch of them for Django:

1. django cms
   
2. mezzanine
   

And more than thirty different ones .

Answer 3

It is unclear why the choice between Django and Pligg.
Django is a Python framework, Pligg is a ready-to-use PHP engine for sites like the one you need. Get Pligg.
Similar topic Which web service development option to choose: Python, Pligg, Ruby?