<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Habari PHP weblog software</title>
	<link>http://www.codescheme.net/2008/05/11/212/</link>
	<description>WordPress, Web Development, Programming</description>
	<pubDate>Sun, 20 Jul 2008 16:21:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Owen</title>
		<link>http://www.codescheme.net/2008/05/11/212/#comment-676</link>
		<dc:creator>Owen</dc:creator>
		<pubDate>Sun, 11 May 2008 15:42:43 +0000</pubDate>
		<guid>http://www.codescheme.net/2008/05/11/212/#comment-676</guid>
		<description>I think you may need to look more closely at how Habari employs PDO.  There are wrapper functions provided by Habari to the relatively obscure PDO operations that mirror WordPress' ez_sql.  So for example, where WordPress uses db_query(), Habari uses DB::query().  Not much different.

PDO is a PHP-native library for database access that is more recent, cross-engine compatible, and more security-minded than the mysql extensions that are used by the WordPress version of ez_sql.  PDO is not a framework, it's a database library, one that will become more standard in PHP applications as developers become more familiar with PHP5.

PHP5 is the way of the future.  5.2 has the best balance of stability and functionality.  Other developers would be wise to standardize on this version.</description>
		<content:encoded><![CDATA[<p>I think you may need to look more closely at how Habari employs PDO.  There are wrapper functions provided by Habari to the relatively obscure PDO operations that mirror WordPress&#8217; ez_sql.  So for example, where WordPress uses db_query(), Habari uses DB::query().  Not much different.</p>
<p>PDO is a PHP-native library for database access that is more recent, cross-engine compatible, and more security-minded than the mysql extensions that are used by the WordPress version of ez_sql.  PDO is not a framework, it&#8217;s a database library, one that will become more standard in PHP applications as developers become more familiar with PHP5.</p>
<p>PHP5 is the way of the future.  5.2 has the best balance of stability and functionality.  Other developers would be wise to standardize on this version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lewis</title>
		<link>http://www.codescheme.net/2008/05/11/212/#comment-674</link>
		<dc:creator>Lewis</dc:creator>
		<pubDate>Sun, 11 May 2008 10:52:31 +0000</pubDate>
		<guid>http://www.codescheme.net/2008/05/11/212/#comment-674</guid>
		<description>Not negative about Habari, coding or intentions - I think at the present time a strongly viable alternative to WordPress has become a definitely 'good thing'. 

The overall caveat I would have is on the issue of included frameworks and packages, in which, only for the purpose here, I'd include PDO - agreed, not an issue for the average webmaster, but probably yes, becoming an issue for the 'average programmer' - WordPress does benefit from its transparency and (indeed) slightly clonky old code - it gives the confidence to a lot of people to hack it around (now whether this is a good thing or not....).

Observations here as gross generalisation - I'll certainly present my opinion, for what it's worth, in better detail...</description>
		<content:encoded><![CDATA[<p>Not negative about Habari, coding or intentions - I think at the present time a strongly viable alternative to WordPress has become a definitely &#8216;good thing&#8217;. </p>
<p>The overall caveat I would have is on the issue of included frameworks and packages, in which, only for the purpose here, I&#8217;d include PDO - agreed, not an issue for the average webmaster, but probably yes, becoming an issue for the &#8216;average programmer&#8217; - WordPress does benefit from its transparency and (indeed) slightly clonky old code - it gives the confidence to a lot of people to hack it around (now whether this is a good thing or not&#8230;.).</p>
<p>Observations here as gross generalisation - I&#8217;ll certainly present my opinion, for what it&#8217;s worth, in better detail&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael C. Harris</title>
		<link>http://www.codescheme.net/2008/05/11/212/#comment-672</link>
		<dc:creator>Michael C. Harris</dc:creator>
		<pubDate>Sun, 11 May 2008 10:03:19 +0000</pubDate>
		<guid>http://www.codescheme.net/2008/05/11/212/#comment-672</guid>
		<description>Thanks for trying out Habari. PDO gives us better security by default, by preventing SQL injection attacks, supports prepared statements, and allows us to support multiple databases (currently MySQL and SQLite, with PostgreSQL support on the way). You don't need to know anything about PDO to be able to use Habari though, only if you want to contribute to the core. Not likely to be an issue for your "average programmer."

Your post ends sounding a bit negative, with your comments about Magento. Did you have any problems with Habari? If you did, we'd love your feedback. Actually, we'd love feedback if there were things you liked as well :)</description>
		<content:encoded><![CDATA[<p>Thanks for trying out Habari. PDO gives us better security by default, by preventing SQL injection attacks, supports prepared statements, and allows us to support multiple databases (currently MySQL and SQLite, with PostgreSQL support on the way). You don&#8217;t need to know anything about PDO to be able to use Habari though, only if you want to contribute to the core. Not likely to be an issue for your &#8220;average programmer.&#8221;</p>
<p>Your post ends sounding a bit negative, with your comments about Magento. Did you have any problems with Habari? If you did, we&#8217;d love your feedback. Actually, we&#8217;d love feedback if there were things you liked as well <img src='http://www.codescheme.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
