3 ms·
I think these are simply "gotchas" rather than reasons not to use django. We've probably all committed an n+1 query at some point, but that doesn't mean the lan
by nomilk 5y ago
I think these are simply "gotchas" rather than reasons not to use django. We've probably all committed an n+1 query at some point, but that doesn't mean the language/framework we were using was bad.
Meta point: I really enjoy articles that list the places noobies go wrong (for any language/framework, not exclusively django). E.g. an experienced dev I taught R to was mind-blown that vec[1] accesses the first element of a vector (not vec[0]).
Long lists of these unexpected (albeit simple) things can quickly be compiled. It might only take 30 minutes for a noobie to read but probably ends up saving days of pain down the track.
- jmconfuzeus 5y agoI never said that people need to stop using Django. It's still my favorite framework and will continue to be. I just wanted to point out some mistakes that many beginners make and that I made when I first started. Personally, I think Django could use better opinions from the core team because beginners should be set for success by default. In the current state, that's not the case.
- nomilk 5y ago> I never said that people need to stop using Django. I know :) I was alluding to that exact point. I think other commenters thought that's what you meant, and jumped to the defence of the framework. But I agree that criticism is healthy, and it doesn't mean you don't enjoy or would stop using it. As someone who hasn't done much django, I appreciate your tips for beginners (especially in list format).