Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!cs.uu.nl!news.stack.nl!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.011 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'subject:Django': 0.03; 'users,': 0.07; 'python': 0.09; 'forcing': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:Why': 0.09; 'thread': 0.11; '"python': 0.16; 'defacto': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'said.': 0.16; 'subject:popular': 0.16; 'wrote:': 0.17; '(not': 0.20; 'header :User-Agent:1': 0.26; 'header:X-Complaints-To:1': 0.28; 'fri,': 0.30; 'thursday,': 0.30; 'feedback': 0.30; 'good.': 0.32; 'johnson': 0.32; 'choices': 0.33; 'to:addr:python-list': 0.33; 'sometimes': 0.35; 'subject:?': 0.35; 'received:org': 0.36; 'but': 0.36; 'should': 0.36; 'charset:us-ascii': 0.36; 'subject:: ': 0.38; 'behind': 0.38; 'to:addr:python.org': 0.39; 'header:Received:5': 0.40; 'end': 0.40; 'your': 0.60; "you've": 0.61; 'back': 0.62; 'dead': 0.62; 'provide': 0.62; 'become': 0.65; 'unnecessary': 0.65; 'directed': 0.81; '2013': 0.84; 'forced': 0.84; 'received:sd.cox.net': 0.84; 'rick': 0.91 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: python-list@python.org To: python-list@python.org From: rh Subject: Re: Why is Ruby on Rails more popular than Django? Date: Fri, 8 Mar 2013 09:12:55 -0800 References: <2fc87695-9d0b-45b3-ae96-98e0591b30a0@googlegroups.com> <3d9fe0b2-7931-4ab6-8929-235460729c64@q9g2000pbf.googlegroups.com> <9748aa63-9b06-4b75-8881-bda43f7c6d4e@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: ip68-227-87-145.sb.sd.cox.net User-Agent: dsodnetnin X-Mailer: EZnn0.37p X-Newsreader: EZnn0.37p X-Gmane-NNTP-Posting-Host: EZnn0.37p Original-Received: from slem by 1.1 with local X-No-Archive: yes Archive: no X-Archive: expiry=11 X-Archive: encrypt X-Operating-System: Barebones_6.1 X-Gmane-NNTP-Posting-Host: 192.168.1.1 X-NNTP-Posting-Host: 192.168.1.1 Mail-Copies-To: never X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 21 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1362762736 news.xs4all.nl 6917 [2001:888:2000:d::a6]:55009 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:40874 On Fri, 8 Mar 2013 08:19:02 -0800 (PST) Rick Johnson wrote: > On Thursday, March 7, 2013 10:50:52 PM UTC-6, rh wrote: > > Choices are good. [...] Having one choice is a mess. And > > look back at history and current events > > Sometimes "choices" are forced upon you without your consent or even > without regard for the end users' well-being. In this case "choices" > are no longer "choices", they become unnecessary dead weight on the > backs of users, they become malevolent multiplicities. So the meme in this thread is "python needs a single web devel. env." And the agenda is "Django should become the defacto python web framework." (a knee-jerk) Forcing a choice is no choice, as you've said. Get behind a choice and submit fixes, provide feedback and/or STFU. (not directed at any single person but at the population)