Andres, amen to most of what you said. Coming to Django from a different place (Scala, Racket), I keep an eye for widely-used good things to come from those communities too. I do like that a Django project found me for work. I just wish I knew more Django! --Geoff
On May 10, 2013, at 12:44 , Andres Osinski <[email protected]> wrote: > I really don't know how you think you'll be getting a different response in > other frameworks, because the core developers' attitude on this is correct. > > There are over 20000 tickets in the bug tracker for a project used by tens of > thousands of people. Code has to pass style guidelines, regression tests, > documentation must be made, features must be integrated into a release > schedule, obscure platform bugs and overall consistency with the rest of the > code has to be verified. > > This takes a *long* time. Adding an extra method to the Model class is > something that may take weeks to discuss and to consider in a myriad possible > aspects. And what's worse, someone after you will have to maintain the whole > thing, because retrospectively removing things is a *really bad* practice on > code that you don't own. > > Discussions take place on the mailing list and chat rooms because bug > trackers are not and have never been a place to discuss design decisions or > implementation details; just a place to track the progress in the development > and status of a bug or feature request. > > Finally, Django as a framework is *massive*, and really good reasons have to > be had in order to increment the line count even more for something that is > ostensibly a corner case for people who don't wish to do a bit of additional > work by working within the framework's constraints and opinions instead of > against them. > > Unfortunately, given that no framework is as large or feature-complete > (Pyramid supports a lot of things, but is against including too much in the > core framework and instead depends on external libs), you'll have even *less* > luck with other pieces of code. And I would certainly distrust any framework > that has less rigor than Django for including features; what core devs > giveth, core devs may deprecate on the next release. > > Also, I beleive your perception of Django's openness if flat-out erroneous. > Go try to add an unrequested feature in Rails or Yii without discussion and > see how you're welcomed, never mind the fact that both of these framework's > development is done completely in the dark for many of the most important > features. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
