3 ms·
The problem is Django itself as a framework and Python as a slow infrastructure for it are getting too old with time. I love Django but it grows too restrictive
by myf01d 10y ago
The problem is Django itself as a framework and Python as a slow infrastructure for it are getting too old with time. I love Django but it grows too restrictive as projects get more complicated (ORM and template rendering for example), not to mention the slow performance compared to new languages like Go and Elixir, which is actually Python's responsibility not Django.
Django is a monolithic framework that wants to do everything while there are good and even superior alternatives(SQlAlchemy, Jinja2, WTForms), which makes things harder for its developers.
- wheelerwj 10y agoi dont know what that has to do with embedding tracking in code. if youre trying to make the point that funding is made more difficult and therefore exacerbates the analytics problem, sure. but isn't that out of scope?
- myf01d 10y agoMaybe, but my point is given that Django is framework from the past, it will be harder to get support unless from big companies that already use it because they want security patches, bug fixes or so.
- kirkdouglas 10y agoYou can easily replace template engine and ORM in Django when your project becomes large. I've personally made this several times.
- nsomaru 10y agoYou easily ripped out the orm and templating engine on a large project? Would love to know how.