<?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/"
	xmlns:georss="http://www.georss.org/georss" 	>
<channel>
	<title>Comments on: Bake-off in progress for LITA blog, and thoughts about Movable Type</title>
	<atom:link href="http://freerangelibrarian.com/2005/03/21/bake-off-in-progress-for-lita-blog-and-thoughts-about-movable-type/feed/" rel="self" type="application/rss+xml" />
	<link>http://freerangelibrarian.com/2005/03/21/bake-off-in-progress-for-lita-blog-and-thoughts-about-movable-type/</link>
	<description>K.G. Schneider's blog on librarianship, writing, and everything else</description>
	<lastBuildDate>Sun, 20 May 2012 03:37:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Richard</title>
		<link>http://freerangelibrarian.com/2005/03/21/bake-off-in-progress-for-lita-blog-and-thoughts-about-movable-type/comment-page-1/#comment-1262</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Tue, 22 Mar 2005 15:37:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.freerangelibrarian.com/2005/03/21/bake-off-in-progress-for-lita-blog-and-thoughts-about-movable-type/#comment-1262</guid>
		<description>I find your comments on MT and WP interesting but they seem to be all about support and marketing issues, not with core code issues.

I started with a very early version of MT and then moved to WordPress early on in its evolution. I think both products and both support environments have good and bad points and neither is a clear winner in my mind.

True, MT is not as dyamic as WP in that it needs to be rebuilt when templates are updated but that&#039;s a development issue and as a weblog/site matures, the days of tweaking code get further apart.

Both products suffer from comment spam. True, 6A has an identity problem about commercial vs. open source but given that the product is not all that expensive and they do provide quality online documentation and a clean and clear website, I&#039;m not sure it&#039;s such a downer to watch them evolve into a commercial software company.

The WP community can be back-biting, egomaniacle, and just as weird in other ways, not to mention that the back end of WP, even 1.5 is a visual abomination: disorganized, poor design, poor layout, and not fully compatible with all browsers.

Maybe the bigger question is this: how long will the popularity of personal publishing (AKA: blogging) last and might there be other content management systems out there on the web that will take the place of these two? Or, will these two evolve into huge, combersome, MS-Office like CMSs and sink to the bottom?

One thig&#039;s for sure: the number of people now online with interesting things to say has skyrocketed and I&#039;m glad of that. We can thank both 6 apart and Matt and the WP community for that.</description>
		<content:encoded><![CDATA[<p>I find your comments on MT and WP interesting but they seem to be all about support and marketing issues, not with core code issues.</p>
<p>I started with a very early version of MT and then moved to WordPress early on in its evolution. I think both products and both support environments have good and bad points and neither is a clear winner in my mind.</p>
<p>True, MT is not as dyamic as WP in that it needs to be rebuilt when templates are updated but that&#8217;s a development issue and as a weblog/site matures, the days of tweaking code get further apart.</p>
<p>Both products suffer from comment spam. True, 6A has an identity problem about commercial vs. open source but given that the product is not all that expensive and they do provide quality online documentation and a clean and clear website, I&#8217;m not sure it&#8217;s such a downer to watch them evolve into a commercial software company.</p>
<p>The WP community can be back-biting, egomaniacle, and just as weird in other ways, not to mention that the back end of WP, even 1.5 is a visual abomination: disorganized, poor design, poor layout, and not fully compatible with all browsers.</p>
<p>Maybe the bigger question is this: how long will the popularity of personal publishing (AKA: blogging) last and might there be other content management systems out there on the web that will take the place of these two? Or, will these two evolve into huge, combersome, MS-Office like CMSs and sink to the bottom?</p>
<p>One thig&#8217;s for sure: the number of people now online with interesting things to say has skyrocketed and I&#8217;m glad of that. We can thank both 6 apart and Matt and the WP community for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dorothea Salo</title>
		<link>http://freerangelibrarian.com/2005/03/21/bake-off-in-progress-for-lita-blog-and-thoughts-about-movable-type/comment-page-1/#comment-1261</link>
		<dc:creator>Dorothea Salo</dc:creator>
		<pubDate>Mon, 21 Mar 2005 19:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.freerangelibrarian.com/2005/03/21/bake-off-in-progress-for-lita-blog-and-thoughts-about-movable-type/#comment-1261</guid>
		<description>And if WordPress tanks, it&#039;s possible to fork the code -- as has, in fact, already been done. Shelley Powers forked the 1.5 version of WordPress to create her own WordForm.

I&#039;d offer help with WordPress, but I must sheepishly confess to not having upgraded to 1.5 yet owing to extreme lack of time.</description>
		<content:encoded><![CDATA[<p>And if WordPress tanks, it&#8217;s possible to fork the code &#8212; as has, in fact, already been done. Shelley Powers forked the 1.5 version of WordPress to create her own WordForm.</p>
<p>I&#8217;d offer help with WordPress, but I must sheepishly confess to not having upgraded to 1.5 yet owing to extreme lack of time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://freerangelibrarian.com/2005/03/21/bake-off-in-progress-for-lita-blog-and-thoughts-about-movable-type/comment-page-1/#comment-1260</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Mon, 21 Mar 2005 18:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.freerangelibrarian.com/2005/03/21/bake-off-in-progress-for-lita-blog-and-thoughts-about-movable-type/#comment-1260</guid>
		<description>This nicely sums up my thoughts about Movable Type. I ran MT on my personal site last year and found out about the new license changes during an upgrade. I was also annoyed at the way the licensing seemed to be rather conveniently crafted to force anyone outside of a single-user to buy the product rather than use the free version. 

I switched to Wordpress and have been just as happy with it as I was with earlier versions of MT. If I&#039;m going to run something where I&#039;m my own technical support, and don&#039;t be fooled by MT&#039;s &quot;support&quot;, 99% of the time you&#039;re still off searching message boards for fixes, I&#039;d rather not pay for that priviledge.

As with any technology decision, I&#039;m sure there will be much handwringing and gnashing of teeth before a choice is made.</description>
		<content:encoded><![CDATA[<p>This nicely sums up my thoughts about Movable Type. I ran MT on my personal site last year and found out about the new license changes during an upgrade. I was also annoyed at the way the licensing seemed to be rather conveniently crafted to force anyone outside of a single-user to buy the product rather than use the free version. </p>
<p>I switched to WordPress and have been just as happy with it as I was with earlier versions of MT. If I&#8217;m going to run something where I&#8217;m my own technical support, and don&#8217;t be fooled by MT&#8217;s &#8220;support&#8221;, 99% of the time you&#8217;re still off searching message boards for fixes, I&#8217;d rather not pay for that priviledge.</p>
<p>As with any technology decision, I&#8217;m sure there will be much handwringing and gnashing of teeth before a choice is made.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.219 seconds -->

