Live data from Hacker News

Ask HN: Where is the Django community?

news.ycombinator.com

31–40 of 167 posts

Re: Ask HN: Where is the Django community?

#31
post #6

Let me tell you the truth, though this will not be popular: Django is not a good framework. It's clumsy, inflexible and restrictive. The community is pretty much dead. If you want to work in ruby, go for ror. If you want to work in python, go for a micro framework like Bottle. I made the mistake of investing a lot of my time in Django. It was not worth it in the end. All my Django projects ended up being a big mess,…

Django works just fine. If you want to build your own framework (e.g. use Bottle) then go for it. Waste [Invest?] the time while the rest of us are busy getting things done.

I don't think that you can compare ANY Python framework (or any framework in any language) with Ruby on Rails. If you write Ruby, use RoR. If you write Python, don't use RoR.

Also, for anyone recommending something like Tornado, please stop. It's NOT THE SAME THING and completely off topic. If you want something micro for a small concise project use Flask.

Re: Ask HN: Where is the Django community?

#32
post #6

Let me tell you the truth, though this will not be popular: Django is not a good framework. It's clumsy, inflexible and restrictive. The community is pretty much dead. If you want to work in ruby, go for ror. If you want to work in python, go for a micro framework like Bottle. I made the mistake of investing a lot of my time in Django. It was not worth it in the end. All my Django projects ended up being a big mess,…

If you have specific constructive criticism I'm quite happy to hear it.

Re: Ask HN: Where is the Django community?

#33
post #6

Let me tell you the truth, though this will not be popular: Django is not a good framework. It's clumsy, inflexible and restrictive. The community is pretty much dead. If you want to work in ruby, go for ror. If you want to work in python, go for a micro framework like Bottle. I made the mistake of investing a lot of my time in Django. It was not worth it in the end. All my Django projects ended up being a big mess,…

This is what I did (Django for one project -> moved to Rails) and second this. I think Django is a lot easier to get started with, but RoR is much more thought out. OP should also read: http://www.scribd.com/doc/37113340/Why-Django-Sucks-and-How-... Which summarizes some of the problems I had with it. Getting components to work was always a custom job; a stark difference compared with the ease of getting Rails compon…

I'll just point out that was one of the major talks at DjangoCon 2010 and the title was meant to be provocative and in good humour. Eric Florenzano was and is a major player in the (allegedly non-existent) Django community.

Re: Ask HN: Where is the Django community?

#34
post #6

Let me tell you the truth, though this will not be popular: Django is not a good framework. It's clumsy, inflexible and restrictive. The community is pretty much dead. If you want to work in ruby, go for ror. If you want to work in python, go for a micro framework like Bottle. I made the mistake of investing a lot of my time in Django. It was not worth it in the end. All my Django projects ended up being a big mess,…

I couldn't agree more. Django's inability to deal elegantly with, for example, development vs. testing vs. production SETTINGS is an obvious drawback. If I have to use third party middleware or apps to deal with inadequacies of a framework, that's a pretty big alarm that something bigger is wrong. I saw bottle just this past week on HN and I'm itching to give it a shot.

This is rediculous.

Everyone's app is different, and so Django is rightly agnostic as to how your settings are stored, and which are loaded.

As for the scope of the problem: dealing with multiple development settings is Section 1, Page 1 of professional programming. It's a solved and trivial problem. This isn't like coding your own ORM or templating language.

Re: Ask HN: Where is the Django community?

#35
post #6

Let me tell you the truth, though this will not be popular: Django is not a good framework. It's clumsy, inflexible and restrictive. The community is pretty much dead. If you want to work in ruby, go for ror. If you want to work in python, go for a micro framework like Bottle. I made the mistake of investing a lot of my time in Django. It was not worth it in the end. All my Django projects ended up being a big mess,…

As someone who's been using Django since the magic removal branch, its documentation is top notch, not to mention the lack of magic makes it very usable, supportable, and build-able on. I can say definitely what's going on from the top layer to the bottom layer without any black box behaviour.

Rails is full of sloppy coding, lots of magic, coders who think that return is an keyword, and bad practices. I have no problem with ruby as a language, even if it takes flexibility a step too far, however the style of coders, and the general "I did something clever and unreadable so I'm awesome" attitude seems to permeate the ruby-verse. Also while many improvements have been made on the ruby interpreters... the performance is STILL lagging behind Python, which as a dynamic language with compiled backend elements, gives languages like Java a run for their money.

Both systems are very powerful, Django has certain batteries included that I find it strange that rails fails to do (namely a plugabble extensible flexible user authentication system) and both have their adherents.

The writer of this original piece is clearly not very up on Django development, the strong community apparently how to write well implemented MVC code. Having spent years working with a variety of frameworks, I've yet to find a place where Django stops you doing what you want (unless its a fundamentally stupid idea).

Re: Ask HN: Where is the Django community?

#36

I'm in this same boat. I decided to go with Python vs Ruby due to what seemed like a better language for Sys Admin scripting. I tried Django in the past and quickly ran into issues after Django Book. I think I might give Bottle and Flask a try and get my project live.

What issues did you run into by the way?

Re: Ask HN: Where is the Django community?

#37
For a long time I debated which framework to pursue in my off time (work is Java/struts blub programming). Python is the first and only programming language that I truly fell in love with, so I've investigated Django and rather like it. But I'm going to the Lone Star ruby conference next month, and I'll be doing the 0 to Rails tutorial. I guess I'm still having a hard time making up my mind. If exposure to live events is the deciding factor, then ruby will win, because I don't see many nearby django events...

Re: Ask HN: Where is the Django community?

#38

tl;dr; (Not meant as a smart-ass comment but...) they're busy building stuff. I think one of the interesting with Django is just how easy it is to get started with it without prior programming knowledge. I believe this has to do with Python itself and the great docs on Djangoproject.com Just start doing the tutorial and voila. This has introduced a large amount of new programmers to Django and Python, making it gain…

I think one of the interesting with Django is just how easy it is to get started with it without prior programming knowledge.

Wait, you're kidding right? Django is positively horrible for beginning programmers because it's a gigantic framework with an insane learning curve, and if you haven't done much/any webdev before it's almost impossible to learn.

Sure, you and i can pick it up in a weekend, but i don't think it's even in the realm of decent for beginning programmers.

Re: Ask HN: Where is the Django community?

#39
post #6

Let me tell you the truth, though this will not be popular: Django is not a good framework. It's clumsy, inflexible and restrictive. The community is pretty much dead. If you want to work in ruby, go for ror. If you want to work in python, go for a micro framework like Bottle. I made the mistake of investing a lot of my time in Django. It was not worth it in the end. All my Django projects ended up being a big mess,…

I have my own pet gripes about Django, but then I have gripes about any framework I've used, Rails included.

However, when I've seen a Django project that's a "huge mess" that's largely due to the incompetence of the developer. A more "rails-y" framework probably suits such developers, as it gives them less leeway to screw up.

Post reply on HN