<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Django&#8217;s tipping point	</title>
	<atom:link href="https://programmingzen.com/djangos-tipping-point/feed/" rel="self" type="application/rss+xml" />
	<link>https://programmingzen.com/djangos-tipping-point/</link>
	<description>Meditations on programming, startups, and technology</description>
	<lastBuildDate>Wed, 25 Feb 2009 23:01:18 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: ????????		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-5623</link>

		<dc:creator><![CDATA[????????]]></dc:creator>
		<pubDate>Wed, 25 Feb 2009 23:01:18 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-5623</guid>

					<description><![CDATA[The last time i took a look at django version 0.95 or 0.96 was released. This was almost 6 months ago if I remember correctly. The problem with this release cycle is that 1.0 is a safe mark regarding api changes.]]></description>
			<content:encoded><![CDATA[<p>The last time i took a look at django version 0.95 or 0.96 was released. This was almost 6 months ago if I remember correctly. The problem with this release cycle is that 1.0 is a safe mark regarding api changes.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: roger		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-4338</link>

		<dc:creator><![CDATA[roger]]></dc:creator>
		<pubDate>Mon, 29 Sep 2008 19:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-4338</guid>

					<description><![CDATA[I really love the clarity of Django. It reminds me of merb/ramaze :)  At the same time I love Ruby.  Python and Ruby are both really nice.  I dislike Rails, however.  Django is clearer.  Perhaps they took lessons from rails&#039; weaknesses?

I would say if you have a large rails site you&#039;ll probably need about 4x as many app boxes as you would if you were running Django.  Possibly because of a slow ruby runtime (the language is so open that it&#039;s hard to optimize a runtime for it).

So Django wins overall for now for large sites.  Most sites aren&#039;t large, however...it&#039;s more balanced for them.

-=R]]></description>
			<content:encoded><![CDATA[<p>I really love the clarity of Django. It reminds me of merb/ramaze 🙂  At the same time I love Ruby.  Python and Ruby are both really nice.  I dislike Rails, however.  Django is clearer.  Perhaps they took lessons from rails&#8217; weaknesses?</p>
<p>I would say if you have a large rails site you&#8217;ll probably need about 4x as many app boxes as you would if you were running Django.  Possibly because of a slow ruby runtime (the language is so open that it&#8217;s hard to optimize a runtime for it).</p>
<p>So Django wins overall for now for large sites.  Most sites aren&#8217;t large, however&#8230;it&#8217;s more balanced for them.</p>
<p>-=R</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Harold		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-3976</link>

		<dc:creator><![CDATA[Harold]]></dc:creator>
		<pubDate>Mon, 23 Jun 2008 14:38:35 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-3976</guid>

					<description><![CDATA[I have a question. We&#039;ve developed/are developing a website in Plone/Zope. It includes my favorites, people should be able to upload audio, video, and create lots of content and share it with friends or collaborate. There are user profiles as well as voting and tagging. 

OK.. now we feel we&#039;re totally wrong with Plone. It doesn&#039;t even have any social components, and just ajaxifying the stuff is difficult. More things that you think are just normal (creating a subdomain for every member, or at least a normal url) are just not easy if not impossible. 

Now later we want to add collaborative filtering, (off the shelf filters but only in php or C, not python) or simply subscribing to people&#039;s activity (voting, recommendations whatever).... is also not simple in Plone. A lot of stuff is stored in a postgresql database, and some in zodb. 
Even our IT team mentions that we make very little use of Plone itself.. just lots of CSS, ajax and some basic processes. 

Obviously we can migrate and maybe we should. Question is to what ? Migrating to Django would probably allow us to re-use a lot of what we have. Migrating to RoR would probably allow us to choose from more providers, tap into a larger community and more mindshare. 

What to do (I understand noone is going to give me a custom answer here.. but perhaps some insights what to think about in choosing either would be possible and already quite helpful ! ) ?]]></description>
			<content:encoded><![CDATA[<p>I have a question. We&#8217;ve developed/are developing a website in Plone/Zope. It includes my favorites, people should be able to upload audio, video, and create lots of content and share it with friends or collaborate. There are user profiles as well as voting and tagging. </p>
<p>OK.. now we feel we&#8217;re totally wrong with Plone. It doesn&#8217;t even have any social components, and just ajaxifying the stuff is difficult. More things that you think are just normal (creating a subdomain for every member, or at least a normal url) are just not easy if not impossible. </p>
<p>Now later we want to add collaborative filtering, (off the shelf filters but only in php or C, not python) or simply subscribing to people&#8217;s activity (voting, recommendations whatever)&#8230;. is also not simple in Plone. A lot of stuff is stored in a postgresql database, and some in zodb.<br />
Even our IT team mentions that we make very little use of Plone itself.. just lots of CSS, ajax and some basic processes. </p>
<p>Obviously we can migrate and maybe we should. Question is to what ? Migrating to Django would probably allow us to re-use a lot of what we have. Migrating to RoR would probably allow us to choose from more providers, tap into a larger community and more mindshare. </p>
<p>What to do (I understand noone is going to give me a custom answer here.. but perhaps some insights what to think about in choosing either would be possible and already quite helpful ! ) ?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Trent		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-3097</link>

		<dc:creator><![CDATA[Trent]]></dc:creator>
		<pubDate>Thu, 10 Apr 2008 19:31:59 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-3097</guid>

					<description><![CDATA[I would like to see django include more database flexibility, like a stable mssql, db2, and odbc.  For new construction and smaller sites mysql, postgres and such are great, but many larger companies run on mssql and db2, which are the other two &quot;big wheels&quot; in the database world, probably more important than sqlite.  I do realize there is work being done on these and I can&#039;t wait to be able to play!]]></description>
			<content:encoded><![CDATA[<p>I would like to see django include more database flexibility, like a stable mssql, db2, and odbc.  For new construction and smaller sites mysql, postgres and such are great, but many larger companies run on mssql and db2, which are the other two &#8220;big wheels&#8221; in the database world, probably more important than sqlite.  I do realize there is work being done on these and I can&#8217;t wait to be able to play!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Mnmer		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-2909</link>

		<dc:creator><![CDATA[Mnmer]]></dc:creator>
		<pubDate>Mon, 31 Mar 2008 13:37:25 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-2909</guid>

					<description><![CDATA[Antonio,

I agree with you...Python has strong selling points...but they&#039;re largely based on implementation and timing. I think python got to where it is today by basically being a cleaner alternative to perl with a solid implementation at the right time and right place...*and* by having an English-speaking community. When Python was rising in popularity, the Ruby community was largely Japanese...even Matz still struggles with the language.  The headstart that Python got led to may libraries being developed.

Look at Ruby and what are the problems? Libraries and implementation (speed). Ruby 1.9 and rubinius should solve the performance problems...I don&#039;t have an answer for the libraries. Hopefully just continued use will provide better !documented! libraries.

Sure there is room for both Python and Ruby, but in a blind &quot;taste&quot; test I believe people will prefer Ruby time  and time again. Python is sort of like Perl to me...when there was nothing else, everything thought perl was the coolest thing. Now, after seeing languages that can be powerful *and* beautiful, everyone wonders what the hell perl programmers were thinking. I read Python docs and think exactly the same thing. There just doesn&#039;t seem to be clarity in the design of the language.]]></description>
			<content:encoded><![CDATA[<p>Antonio,</p>
<p>I agree with you&#8230;Python has strong selling points&#8230;but they&#8217;re largely based on implementation and timing. I think python got to where it is today by basically being a cleaner alternative to perl with a solid implementation at the right time and right place&#8230;*and* by having an English-speaking community. When Python was rising in popularity, the Ruby community was largely Japanese&#8230;even Matz still struggles with the language.  The headstart that Python got led to may libraries being developed.</p>
<p>Look at Ruby and what are the problems? Libraries and implementation (speed). Ruby 1.9 and rubinius should solve the performance problems&#8230;I don&#8217;t have an answer for the libraries. Hopefully just continued use will provide better !documented! libraries.</p>
<p>Sure there is room for both Python and Ruby, but in a blind &#8220;taste&#8221; test I believe people will prefer Ruby time  and time again. Python is sort of like Perl to me&#8230;when there was nothing else, everything thought perl was the coolest thing. Now, after seeing languages that can be powerful *and* beautiful, everyone wonders what the hell perl programmers were thinking. I read Python docs and think exactly the same thing. There just doesn&#8217;t seem to be clarity in the design of the language.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Antonio Cangiano		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-2897</link>

		<dc:creator><![CDATA[Antonio Cangiano]]></dc:creator>
		<pubDate>Mon, 31 Mar 2008 01:42:19 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-2897</guid>

					<description><![CDATA[While I don&#039;t find Python ugly Mnmer, for the way my mind works, Ruby is cleaner and I do agree that it is, in my opinion, more consistent. I generally prefer Ruby to Python for pretty much any programming task, but that said I recognize Python&#039;s strong selling points and Django&#039;s value and productivity level.]]></description>
			<content:encoded><![CDATA[<p>While I don&#8217;t find Python ugly Mnmer, for the way my mind works, Ruby is cleaner and I do agree that it is, in my opinion, more consistent. I generally prefer Ruby to Python for pretty much any programming task, but that said I recognize Python&#8217;s strong selling points and Django&#8217;s value and productivity level.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Mnmer		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-2896</link>

		<dc:creator><![CDATA[Mnmer]]></dc:creator>
		<pubDate>Mon, 31 Mar 2008 00:32:04 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-2896</guid>

					<description><![CDATA[I am a long time programmer...I started in C, then Perl, then Java, then Tcl, then Python, then more Java, and finally...Ruby.

I have recently started Python again because I have a need that Twisted fulfills rather nicely. I have read the online tutorials, studied Python in a Nutshell, and have a very good grasp on the language.

Let me say this very clearly...once you have tried Ruby, most other languages seem ugly. Python, unfortunately, is painted by this broad brush. I really, really tried to like it, but it is a language that severely lacks clarity.

I see many people comment on the clarity of Python, which I think can really only be attributed to two things: significant whitespace and the enforcement of parentheses in method calls. Other than these two features, the language is a mess. The inconsistency of the object model, the fact that there are new objects and old objects, the __builtin__ methods, the metaprogramming facilities...it all adds up to a LOT that you have to keep in your head when developing.

Contrast this with Ruby, where the object model is simple and clean, there are no builtins (i.e., everything is a message to an object), the metaprogramming facilities are relatively easy to grok, and Ruby has true closures...there&#039;s really no comparison.

I like pythonistas and the #irc channels of Python, Twisted and Django have a great bunch of folks there. However, many times Ruby is criticized when they haven&#039;t spent any time doing it. Ruby is a real improvement upon Python as a langugage (implementation aside).

I do like things about Python. I wouldn&#039;t mind having significant whitespace in Ruby...and I see the lack of parentheses enforcement abused too many times. 

Anyway, I hope those who are critical of Ruby will take the time to use it. I think you&#039;ll find it hard to remove from your frame of reference.]]></description>
			<content:encoded><![CDATA[<p>I am a long time programmer&#8230;I started in C, then Perl, then Java, then Tcl, then Python, then more Java, and finally&#8230;Ruby.</p>
<p>I have recently started Python again because I have a need that Twisted fulfills rather nicely. I have read the online tutorials, studied Python in a Nutshell, and have a very good grasp on the language.</p>
<p>Let me say this very clearly&#8230;once you have tried Ruby, most other languages seem ugly. Python, unfortunately, is painted by this broad brush. I really, really tried to like it, but it is a language that severely lacks clarity.</p>
<p>I see many people comment on the clarity of Python, which I think can really only be attributed to two things: significant whitespace and the enforcement of parentheses in method calls. Other than these two features, the language is a mess. The inconsistency of the object model, the fact that there are new objects and old objects, the __builtin__ methods, the metaprogramming facilities&#8230;it all adds up to a LOT that you have to keep in your head when developing.</p>
<p>Contrast this with Ruby, where the object model is simple and clean, there are no builtins (i.e., everything is a message to an object), the metaprogramming facilities are relatively easy to grok, and Ruby has true closures&#8230;there&#8217;s really no comparison.</p>
<p>I like pythonistas and the #irc channels of Python, Twisted and Django have a great bunch of folks there. However, many times Ruby is criticized when they haven&#8217;t spent any time doing it. Ruby is a real improvement upon Python as a langugage (implementation aside).</p>
<p>I do like things about Python. I wouldn&#8217;t mind having significant whitespace in Ruby&#8230;and I see the lack of parentheses enforcement abused too many times. </p>
<p>Anyway, I hope those who are critical of Ruby will take the time to use it. I think you&#8217;ll find it hard to remove from your frame of reference.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: perl hacker		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-2808</link>

		<dc:creator><![CDATA[perl hacker]]></dc:creator>
		<pubDate>Mon, 24 Mar 2008 01:41:28 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-2808</guid>

					<description><![CDATA[Try these queries instead:

perl language: 1,710,000
perl programming: 5,960,000
catalyst framework: 578,000

AFAIK there is only one Catalyst book

Catalyst offers both a choice of ORMs and a choice of template language]]></description>
			<content:encoded><![CDATA[<p>Try these queries instead:</p>
<p>perl language: 1,710,000<br />
perl programming: 5,960,000<br />
catalyst framework: 578,000</p>
<p>AFAIK there is only one Catalyst book</p>
<p>Catalyst offers both a choice of ORMs and a choice of template language</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dyadya Zed		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-2784</link>

		<dc:creator><![CDATA[Dyadya Zed]]></dc:creator>
		<pubDate>Sat, 22 Mar 2008 11:00:58 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-2784</guid>

					<description><![CDATA[Here is an english version description for mysql_cluster http://softwaremaniacs.org/soft/mysql_cluster/en/]]></description>
			<content:encoded><![CDATA[<p>Here is an english version description for mysql_cluster <a href="http://softwaremaniacs.org/soft/mysql_cluster/en/" rel="nofollow ugc">http://softwaremaniacs.org/soft/mysql_cluster/en/</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Yahoo! UI (YUI) + Django templates == Google Code project! FTW! &#124; Ryan Kanno: The diary of an Enginerd in Hawaii		</title>
		<link>https://programmingzen.com/djangos-tipping-point/#comment-2783</link>

		<dc:creator><![CDATA[Yahoo! UI (YUI) + Django templates == Google Code project! FTW! &#124; Ryan Kanno: The diary of an Enginerd in Hawaii]]></dc:creator>
		<pubDate>Fri, 21 Mar 2008 19:57:12 +0000</pubDate>
		<guid isPermaLink="false">http://antoniocangiano.com/2008/03/20/djangos-tipping-point/#comment-2783</guid>

					<description><![CDATA[[...] out the project here. I know, I know - nothing revolutionary here, but I figure since Django is picking up some steam, these templates might help a Djangonaut get a head start on their next million dollar [...]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] out the project here. I know, I know &#8211; nothing revolutionary here, but I figure since Django is picking up some steam, these templates might help a Djangonaut get a head start on their next million dollar [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
