Hi Karol,
On Saturday 18 May 2013 13:26:53 Karol Sikora wrote:
> Hi,
>
> We was talked with Russell on djangocon eu about integrating more rich
> support for working django as rest api provider, focused on dealing with
> one-page web applications.
> The motivations that currently without third party modules like
> django-rest-framework or tastypie its quite impossible to create rich web
> applications working as one-page.
> As django aims to follow "batteries included" philosophy, so maybe it will
> be a good idea to integrate support for dealing with modern web
> applications.
>
My understanding of Django's philosophy is quite different; in contrast to what
you imply, I think that the rich eco-system of 3rd-party packages, including
mini-frameworks, is one Django's important strengths.
In other words, I don't see the requirement to use a third-party module as a
problem in itself. If this requirement causes you some other problems, please
explain what they are.
Other than that, I read your suggestion as "let's make a new REST-API mini-
framework, but make it in core". That's not the way Django has done such
things in the past -- usually, a third-party package that gained wide
acceptance, to the point that it was a de-facto standard, is then accepted
into core. A classic example for this is staticfiles. Currently, as far as I
can see, there is no clear "winner" in this space -- django-rest-framework and
tastypie are both strong contenders; so we're not in a good position to take
one of them in, and certainly not in position to throw them both out.
And further -- unless I missed something, there is nothing in your current
suggestion that cannot be implemented as a third-party package. You are more
than welcome to do just that -- perhaps you will be able to do something that
convinces core to include it; but you should do this with code, not plans. I
am pretty certain that you will not get any guarantee that your code will be
included, until core developers can see it.
If I misunderstood your suggestion, please clarify it; if there is anything
missing in core for you to implement your suggestion, please ask for it --
Django has been pretty receptive for changes that make it more extensible and
adaptable.
Hope this helps,
Shai.
--
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.
