<?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"
	>
<channel>
	<title>Comments on: Why the webstandards world appears to be choosing Django</title>
	<atom:link href="http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/feed/" rel="self" type="application/rss+xml" />
	<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/</link>
	<description>Morethanseven is where Gareth Rushgrove plays with the web</description>
	<pubDate>Fri, 08 Aug 2008 20:52:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Django reaching its tipping point? &#124; What did you mean ?</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8876</link>
		<dc:creator>Django reaching its tipping point? &#124; What did you mean ?</dc:creator>
		<pubDate>Wed, 30 Jul 2008 10:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8876</guid>
		<description>[...] of chatter recently about the web standards crowd choosing Django and the growing Django trend. And when it hits 1.0 this year the buzz will only get louder.  [...]</description>
		<content:encoded><![CDATA[<p>[...] of chatter recently about the web standards crowd choosing Django and the growing Django trend. And when it hits 1.0 this year the buzz will only get louder.  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam J</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8864</link>
		<dc:creator>Sam J</dc:creator>
		<pubDate>Thu, 17 Jul 2008 11:45:20 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8864</guid>
		<description>I'm a Ruby on Rails junkie but am not religious about it so when AppEngine came along I had good enough reason to take another look at Django. In any case I'll continue to choose the right tool for the job, whatever that may be.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a Ruby on Rails junkie but am not religious about it so when AppEngine came along I had good enough reason to take another look at Django. In any case I&#8217;ll continue to choose the right tool for the job, whatever that may be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morethanseven &#187; Of Hacking, Continuous Integration and Django</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8850</link>
		<dc:creator>Morethanseven &#187; Of Hacking, Continuous Integration and Django</dc:creator>
		<pubDate>Sat, 21 Jun 2008 18:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8850</guid>
		<description>[...] to Twitter using PHPWhy the webstandards world appears to be choosing DjangoDebug web pages with Jquery and JashWho loses out to X-UA-Compatible?Continuous Integration for [...]</description>
		<content:encoded><![CDATA[<p>[...] to Twitter using PHPWhy the webstandards world appears to be choosing DjangoDebug web pages with Jquery and JashWho loses out to X-UA-Compatible?Continuous Integration for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: araba</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8766</link>
		<dc:creator>araba</dc:creator>
		<pubDate>Tue, 06 May 2008 19:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8766</guid>
		<description>I like python and I've tested Django. Its really nice to play with it but  how extensible is it? I am using Zend Framework because I think it's really flexible. I build a higher level framework on top of Zend Framework. It don't say "You have to do this in this way?", you can create your own logic.</description>
		<content:encoded><![CDATA[<p>I like python and I&#8217;ve tested Django. Its really nice to play with it but  how extensible is it? I am using Zend Framework because I think it&#8217;s really flexible. I build a higher level framework on top of Zend Framework. It don&#8217;t say &#8220;You have to do this in this way?&#8221;, you can create your own logic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-04-30 at Ip&#8217;s</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8756</link>
		<dc:creator>links for 2008-04-30 at Ip&#8217;s</dc:creator>
		<pubDate>Wed, 30 Apr 2008 19:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8756</guid>
		<description>[...] Why the webstandards world appears to be choosing Django (tags: article programming python standards webdesign webstandards django comparison rubyonrails) [...]</description>
		<content:encoded><![CDATA[<p>[...] Why the webstandards world appears to be choosing Django (tags: article programming python standards webdesign webstandards django comparison rubyonrails) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: elliottcable</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8662</link>
		<dc:creator>elliottcable</dc:creator>
		<pubDate>Mon, 14 Apr 2008 09:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8662</guid>
		<description>I love ruby. I hate rails... I am a 'frontend loving' type as you put it. I love good design and semantic markup.

Yet, I do all of my markup in Haml and SASS. Haml, I am far less enamored of than SASS... but SASS is just plain fuckin' sex incarnate. You say you ENJOY writing CSS? I say, bullshit.

HTML, well... it's quite verbose. Overly verbose. That just comes with the XML territory. But it's nice, to be able to save half my time with Haml. I don't always write in Haml, not when I'm just popping out a single page to describe something (elliottcable.name/contact.xhtml, rubydie.com) but I would never do an entire site by hand in HTML any more. Not when I can do it in Haml, require bits back and forth left and right in normal ruby, iterate repetitive sections, not worry about closing elements or wrapping structure... it's made my life quite easier.

Rail on rails (hehe) all you want, but watch your footing with Haml and SASS. They are gods incarnate in this land of developers. Short them, and ware ye the six and a quarter hells I will bring precipitating down on your head.

Okay... so maybe not. But I seriously think you need to take a second look at them. You seem to have been ruined for the Ruby language by only seeing the Rails part of our community/code... you should jump into some of the OTHER Ruby frameworks, there's a lot of 'Good' out there - more than more than more than enough to offset the Rails 'Bad'. Check out Merb, Mack, Ramaze, and Sinatra for instance, they're all very sexy - though Merb is the best of the bunch imho.</description>
		<content:encoded><![CDATA[<p>I love ruby. I hate rails&#8230; I am a &#8216;frontend loving&#8217; type as you put it. I love good design and semantic markup.</p>
<p>Yet, I do all of my markup in Haml and SASS. Haml, I am far less enamored of than SASS&#8230; but SASS is just plain fuckin&#8217; sex incarnate. You say you ENJOY writing CSS? I say, bullshit.</p>
<p>HTML, well&#8230; it&#8217;s quite verbose. Overly verbose. That just comes with the XML territory. But it&#8217;s nice, to be able to save half my time with Haml. I don&#8217;t always write in Haml, not when I&#8217;m just popping out a single page to describe something (elliottcable.name/contact.xhtml, rubydie.com) but I would never do an entire site by hand in HTML any more. Not when I can do it in Haml, require bits back and forth left and right in normal ruby, iterate repetitive sections, not worry about closing elements or wrapping structure&#8230; it&#8217;s made my life quite easier.</p>
<p>Rail on rails (hehe) all you want, but watch your footing with Haml and SASS. They are gods incarnate in this land of developers. Short them, and ware ye the six and a quarter hells I will bring precipitating down on your head.</p>
<p>Okay&#8230; so maybe not. But I seriously think you need to take a second look at them. You seem to have been ruined for the Ruby language by only seeing the Rails part of our community/code&#8230; you should jump into some of the OTHER Ruby frameworks, there&#8217;s a lot of &#8216;Good&#8217; out there &#8211; more than more than more than enough to offset the Rails &#8216;Bad&#8217;. Check out Merb, Mack, Ramaze, and Sinatra for instance, they&#8217;re all very sexy &#8211; though Merb is the best of the bunch imho.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morethanseven &#187; DSLs for HTML and CSS - The Future, or Just Plain Wrong?</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8642</link>
		<dc:creator>Morethanseven &#187; DSLs for HTML and CSS - The Future, or Just Plain Wrong?</dc:creator>
		<pubDate>Fri, 11 Apr 2008 15:20:46 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8642</guid>
		<description>[...] to Twitter using PHPWhy the webstandards world appears to be choosing DjangoDebug web pages with Jquery and JashWho loses out to X-UA-Compatible?Continuous Integration for [...]</description>
		<content:encoded><![CDATA[<p>[...] to Twitter using PHPWhy the webstandards world appears to be choosing DjangoDebug web pages with Jquery and JashWho loses out to X-UA-Compatible?Continuous Integration for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: django и google — software simian's typewritings</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8631</link>
		<dc:creator>django и google — software simian's typewritings</dc:creator>
		<pubDate>Tue, 08 Apr 2008 19:07:40 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8631</guid>
		<description>[...] забавное совпадение: вначале Gareth Rushgrove написал статью «Why the webstandards world appears to be choosing Django», а потом, буквально через несколько дней, гугл [...]</description>
		<content:encoded><![CDATA[<p>[...] забавное совпадение: вначале Gareth Rushgrove написал статью «Why the webstandards world appears to be choosing Django», а потом, буквально через несколько дней, гугл [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergei Mutovkin&#8217;s Rumbling Mumbling &#187; Another reason for Django</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8614</link>
		<dc:creator>Sergei Mutovkin&#8217;s Rumbling Mumbling &#187; Another reason for Django</dc:creator>
		<pubDate>Sun, 06 Apr 2008 23:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8614</guid>
		<description>[...] in the subject is my own mental point in the unordered list. This reason is the proper appreciation of web standards by the [...]</description>
		<content:encoded><![CDATA[<p>[...] in the subject is my own mental point in the unordered list. This reason is the proper appreciation of web standards by the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tore Darell</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8613</link>
		<dc:creator>Tore Darell</dc:creator>
		<pubDate>Sun, 06 Apr 2008 22:27:08 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8613</guid>
		<description>Oh yeah, about HAML and SASS - as someone else said they're definitely not there to take away anything from HTML and CSS - or should I say the DOM (element tree), because that's what it's really about. HTML and CSS are syntaxes for describing and accessing the tree of elements, and they're both very verbose. HAML and SASS are just different ways to represent the DOM in a more concise, readable and structured manner. HAML and SASS files contain exactly the same semantics as their HTML and CSS equivalents.

SASS represents a typical point where designers and programmers approach something differently. I'm constantly amazed when I see that well-known web designer's style sheets have no structure at all (and still their designs are far better than anything I could come up with :-). The programmer in me makes me structure my CSS hierarchically (representing the DOM tree), and doing it manually was a major PITA with lots of repetition (and programmers hate repetition). SASS structures my CSS without making me repeat myself, and the end result is the same.</description>
		<content:encoded><![CDATA[<p>Oh yeah, about HAML and SASS &#8211; as someone else said they&#8217;re definitely not there to take away anything from HTML and CSS &#8211; or should I say the DOM (element tree), because that&#8217;s what it&#8217;s really about. HTML and CSS are syntaxes for describing and accessing the tree of elements, and they&#8217;re both very verbose. HAML and SASS are just different ways to represent the DOM in a more concise, readable and structured manner. HAML and SASS files contain exactly the same semantics as their HTML and CSS equivalents.</p>
<p>SASS represents a typical point where designers and programmers approach something differently. I&#8217;m constantly amazed when I see that well-known web designer&#8217;s style sheets have no structure at all (and still their designs are far better than anything I could come up with :-). The programmer in me makes me structure my CSS hierarchically (representing the DOM tree), and doing it manually was a major PITA with lots of repetition (and programmers hate repetition). SASS structures my CSS without making me repeat myself, and the end result is the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pharaos World</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8600</link>
		<dc:creator>Pharaos World</dc:creator>
		<pubDate>Sun, 06 Apr 2008 11:12:09 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8600</guid>
		<description>[...] prefer [...]</description>
		<content:encoded><![CDATA[<p>[...] prefer [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neutral</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8594</link>
		<dc:creator>Neutral</dc:creator>
		<pubDate>Sat, 05 Apr 2008 19:02:14 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8594</guid>
		<description>I don't use Django or Rails, so this is just my impression as an outsider. It might not be the correct impression, but this is what I see.

PHP code gives you a lot of freedom, but the results can be quite messy if it is written by an unstructured programmer. Rails got a lot of early hype with its MVC method and "build a blog in X minutes" videos. This attracted many PHP coders who were shocked and awe. Some of them have never recovered from the shock and continue spreading the "rails way".

Combined with a few Web 2.0 companies, at the time when Web 2.0 was given a name, and that Rails was backed by a company, this attracted even more PHP coders and Java coders to the platform.

I have the impression that Python coders were generally experienced programmers and people with a varied experience. Since Rails attracted most of the bad PHP coders, the Python community was spared the "barbarian hordes". Many of the new developments made by Pythonistas, really show a commitment to existing standards. When I read intelligent articles about standards, it is more likely to be followed by a Python code example, than Rails.

I'm not saying that ALL rails coders are bad. I see lots of great code and standards compliant web sites out there. But it has a much greater share of former spaghetti/self-taught/script kiddies who have "seen the light".</description>
		<content:encoded><![CDATA[<p>I don&#8217;t use Django or Rails, so this is just my impression as an outsider. It might not be the correct impression, but this is what I see.</p>
<p>PHP code gives you a lot of freedom, but the results can be quite messy if it is written by an unstructured programmer. Rails got a lot of early hype with its MVC method and &#8220;build a blog in X minutes&#8221; videos. This attracted many PHP coders who were shocked and awe. Some of them have never recovered from the shock and continue spreading the &#8220;rails way&#8221;.</p>
<p>Combined with a few Web 2.0 companies, at the time when Web 2.0 was given a name, and that Rails was backed by a company, this attracted even more PHP coders and Java coders to the platform.</p>
<p>I have the impression that Python coders were generally experienced programmers and people with a varied experience. Since Rails attracted most of the bad PHP coders, the Python community was spared the &#8220;barbarian hordes&#8221;. Many of the new developments made by Pythonistas, really show a commitment to existing standards. When I read intelligent articles about standards, it is more likely to be followed by a Python code example, than Rails.</p>
<p>I&#8217;m not saying that ALL rails coders are bad. I see lots of great code and standards compliant web sites out there. But it has a much greater share of former spaghetti/self-taught/script kiddies who have &#8220;seen the light&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casey</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8593</link>
		<dc:creator>Casey</dc:creator>
		<pubDate>Sat, 05 Apr 2008 18:27:22 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8593</guid>
		<description>I think that you may have missed the mark on HAML - HAML and SASS exist *because* of a love for HTML and CSS and it was written specifically to make UI/frontend designers as happy as possible.

HAML promotes very good habits when it comes to standards and it takes you away from having ugly views (both before and after rendering)</description>
		<content:encoded><![CDATA[<p>I think that you may have missed the mark on HAML &#8211; HAML and SASS exist <strong>because</strong> of a love for HTML and CSS and it was written specifically to make UI/frontend designers as happy as possible.</p>
<p>HAML promotes very good habits when it comes to standards and it takes you away from having ugly views (both before and after rendering)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Holden</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8588</link>
		<dc:creator>Steve Holden</dc:creator>
		<pubDate>Sat, 05 Apr 2008 12:05:48 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8588</guid>
		<description>@Rabbit: I agree that we should, as web technologists, understand as much about web technologies as we can. But this doesn't stop me from very definitely being an "engine room guy" - any design I produce will be somewhere between pedestrian and ugly, because my design skills aren't graphical in nature - I build code, that's what I am good at, and there are relatively few individuals who are good at both graphical *and* software design.

More generally, as a long-time Python user I was attracted to Django (having written a book about Python Web Programming) because it made a great decision about the split between computation and markup. I was amazed at how easy it was to build a relatively complex page structure automatically from the database and embed guaranteed-correct navigation structures into the basic template, which was then inherited by all page designs.

This didn't happen by accident: the Ellington system was specifically designed to be useful to designers with no programming experience, and allows them to easily specify designs that programmers can easily populate: there's just enough variability in the templating system for a designer to be able to wrap their head around it.</description>
		<content:encoded><![CDATA[<p>@Rabbit: I agree that we should, as web technologists, understand as much about web technologies as we can. But this doesn&#8217;t stop me from very definitely being an &#8220;engine room guy&#8221; &#8211; any design I produce will be somewhere between pedestrian and ugly, because my design skills aren&#8217;t graphical in nature &#8211; I build code, that&#8217;s what I am good at, and there are relatively few individuals who are good at both graphical <strong>and</strong> software design.</p>
<p>More generally, as a long-time Python user I was attracted to Django (having written a book about Python Web Programming) because it made a great decision about the split between computation and markup. I was amazed at how easy it was to build a relatively complex page structure automatically from the database and embed guaranteed-correct navigation structures into the basic template, which was then inherited by all page designs.</p>
<p>This didn&#8217;t happen by accident: the Ellington system was specifically designed to be useful to designers with no programming experience, and allows them to easily specify designs that programmers can easily populate: there&#8217;s just enough variability in the templating system for a designer to be able to wrap their head around it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen Scott &#187; I&#8217;ve used Rails. It seemed a good idea at the time.</title>
		<link>http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8585</link>
		<dc:creator>Glen Scott &#187; I&#8217;ve used Rails. It seemed a good idea at the time.</dc:creator>
		<pubDate>Sat, 05 Apr 2008 00:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://morethanseven.net/posts/why-the-webstandards-world-appears-to-be-choosing-django/#comment-8585</guid>
		<description>[...] Morethanseven » Why the webstandards world appears to be choosing Django [...]</description>
		<content:encoded><![CDATA[<p>[...] Morethanseven » Why the webstandards world appears to be choosing Django [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
