> > Vito, I know you're trying to help, but at this point your coming > across with a strong tone of entitlement, and you're chastising us > without actually having contributed anything concrete. If you really > want to help, then contribute. >
I have to agree with Jacob here (not that my opinion counts for much). The last few threads have just been a vague "Django should support new technologies", but the only concrete example was Bigtable on GAE. First, Django was included in GAE so that developers could use the templating language and views. It was never a push by Google to get Django to develop their ORM to meet the needs of their Bigtable design. Secondly, I use app-engine-patch pretty heavily now, and I think it's great. Sure, it's not in the core, and it's not the most ideal solution, but it definitely works, and I have to consider GAE a pretty niche market, to be honest. Not to mention that, from what I understand, the creators of AEP are working on some new stuff that will make the integration even more seamless. That being said, I think if you want to see a "new feature" that you must have in the Django core, going about it with the tone of "how could this not already be in the core" probably won't buy you much. Proposing potential solutions and starting relevant, well articulated discussions on the topic might get the ball rolling in that direction though. Just my $0.02. -- Brian O'Connor -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
