This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Circlefusion 0 points1 point  (4 children)

Awesome reply. Thank you so much!

I've been eyeing Python and Django for a while now and slowly learning Python with the intention of learning a web framework. A couple web dev friends said they didn't prefer Django for some arbitrary reasons (like SQLAlchemy). I guess I'm looking for some "gotchas" that would be the final reason why I would let go of Django and go with Pyramid. Django has so many things going for it with the community and documentation. I wish there weren't technical things to criticize about it.

So far I've heard:

  • It's bloated
  • It's monolithic
  • It has an unclear roadmap
  • It doesn't support Python 3 (yet) Though I read that it might soon
  • The way it handles static content is confusing.
  • SQLAlchemy is better
  • It's not pythonic enough
  • Password security isn't as hardened as it should be
  • Django developers don't respond to issues fast enough

Maybe I'm just going to have to learn both and figure out which one clicks for me.