News for hackers. Stuff that matters.
Re:Django's Architecture: The Good, The Bad, and The Ugly by k_bx on Sunday June 16, 2013 @04:35AM (#5887866)
For me, the worst thing about django is it's source code. Every time I have to dig into some problem, I see really long functions with multiple abstraction levels mixed, a lot of strange names and other code that is really hard to read (ok, it's still python, so you still can read everything after a bit of tryings).
Re:Django's Architecture: The Good, The Bad, and The Ugly by obviouslygreen on Sunday June 16, 2013 @09:29AM (#5888349)
Not trying to be disparaging, but how much experience do you have working with Python and the libraries that are built with it? I routinely hit the source to see where things are going while working through stack traces or extending built-ins, and while it's not always crystal clear, I've rarely gotten the impression things were done in such a way as to be entirely unreadable or unforgivably abstracted.
Re:Django's Architecture: The Good, The Bad, and The Ugly by k_bx on Monday June 17, 2013 @03:50AM (#5891953)
I have lots of experience with python (>5 years, and +5 years of web-dev before that) and I have no problem reading some of challenging source code out there of course. I'm rather referring to quality of code itself from the perspective of Robert Martin's "Clean Code". I can't remember concrete bits of course, but it sure happened in past.
Re:Django's Architecture: The Good, The Bad, and The Ugly by airtonix on Sunday June 16, 2013 @09:24AM (#5888337)
Perhaps you're the only one? I have no problems reading and working out what's going on (I'm not even what you would call a great programmer)