That was so long I can't even remember what I read. On 10/4/12, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Hey folks -- > > This thread's pretty off-topic for django-dev. Can you please take it > elsewhere? Thanks. > > Jacob > > On Thu, Oct 4, 2012 at 12:49 PM, Amirouche Boubekki > <amirouche.boube...@gmail.com> wrote: >>> Are the Hello world applications are strictly the same (sessions, auth >>> etc) ? >> >> >> The code is available on bitbucket. They are simple hello word apps, a >> view >> which returns a «Hello World» string as body response. >> >>> I still can't see why people wast so much time in such biased "Hello >>> world" tests to claim a definitive "X is the fastest Python web >>> Framework." >> >> >> I still can't understand why people wast so much time claiming the work >> of >> others is useless because you actually mean useless, isn't it ? >> >> >>> Database optimization, ORM, API quality, documentation, libraries, >>> security. >> >> >> I take for granted that at least you have some notions of what makes a >> good >> Web framework. But, Is there any verb that I should guess to make it >> possible to build conversation about this statement ? In particular, what >> do >> you mean by API quality, because that is a particular area I'd like to >> improve. >> >>> Does your framework allow users to deliver in a limited time ? That is >>> the >>> true question. >> >> >> Huhu! I think you are refering to the old line «Web framework for >> perfectionnist with deadlines» which was well translated in french and >> with >> a formulation which can stands time and projects as «Web framework for >> perfectionnist in a hurry». It was maybe a legit claim 7 years ago >> (almost >> ten and two hundreds years at the Web scale) because all solutions at >> that >> time were bloated, broken, not as cool or simply not as good as Django, >> but >> today is almost 2013. Don't expect people to sit down and wait for Django >> to >> leave 1.0 branch to rework the template engine, get rid of managers, >> provide >> a framework for asynchronous tasks that implements ack and doesn't try to >> delete faulty tasks because they expired, reconsider what can be done in >> Django to make the life of frontend developpers easier regarding the >> pervasive use of Javascript clients, provide a framework for service >> oriented applications, take into consideration multiple user editing in >> the >> admin, multiple databases transactions if doesn't already, make it work >> on >> Python 3, make the admin even more hack-friendly, validate/testify any >> other >> useful apps that are nowdays taken for standards in webdev and be simply >> better at what it does already well, I agree, and start eating market >> shares >> of self proclaimed entreprise solutions™. Otherwise said, simply impress >> me >> again and stands out or consider the fact that today Django is just like >> any >> other Python Web framework, no more, no less, with a good documentation >> and >> numerous zealots. It maybe be superflus to look for speed when there is >> other more useful/important/sexy work to do, but it might also not be >> possible to do this improvement without forking or starting from scratch. >> >> The project you are talking about got its fair number of critisism on >> Python >> ML thread already. Do you think this guy is stupid? He was simply >> starting >> to market his work with a simple benchmark no more, no less, and I'd bet >> it >> perform well on full applications too. Most probably he was hacking in >> his >> garage with an idea, getting a Python framework out and make it as good >> as >> Django and maybe better. And according to the numbers we have now it is, >> according the the template syntax it is (or you like to write parsers in >> Python), according the well crafted and separated repositories it is >> (maybe >> a personal preference I agree). You can take for granted that this >> framework >> doesn't have an admin area yet, and couldn't make the mistake of >> recomputing >> most urls for every request, making it useless for any user-facing >> private >> area of reasonable scale, yay, there are top notch admin projects out >> there >> that integrate recognized html5 frameworks of today, but I agree this is >> a >> minor issue for people ready do write some code instead of sneaking into >> the >> admin. According to you not only this guy may be stupid, but his work >> might >> be useless. Maybe you do not know what competition is ? Or, you don't >> know >> what free and open source software is ? It looks like the latter is true >> at >> least contributing code doesn't seem to be part of your agenda or maybe >> your >> are too much concerned about putting down the work of others and making >> zillions out of the work of some. But I guess you are just venting and >> not >> improving the discussion at all. Most probably because you cannot do «un >> pouillème» of what this guy did and of what I hope he will do, you are >> well >> behind this guy in terms of contributions not only for free and open >> source >> industry but also Python and Django in particular. You may (or someone >> else >> will) argue about it being junk-code or code pollution, my bad, this >> exact >> disease did not serve the Javascript and PHP community that badly when >> one >> compares market penetration. The only pollution I know is the shitload of >> thinking patterns people like you have in reserve. >> >> >> >> Amirouche >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To post to this group, send email to django-developers@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. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@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. > >
-- Sent from my mobile device -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
