<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Angelo Bertolli &#187; WordPress</title>
	<atom:link href="http://bertolli.org/category/computer/wordpress/feed" rel="self" type="application/rss+xml" />
	<link>http://bertolli.org</link>
	<description>Cogito ergo sum.</description>
	<lastBuildDate>Sat, 24 Jul 2010 02:58:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Is WordPress Becoming Bloated?</title>
		<link>http://bertolli.org/wordpress-bloated</link>
		<comments>http://bertolli.org/wordpress-bloated#comments</comments>
		<pubDate>Fri, 02 Apr 2010 19:08:00 +0000</pubDate>
		<dc:creator>Angelo</dc:creator>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://bertolli.org/wordpress-bloated</guid>
		<description><![CDATA[I like WordPress&#8211;a lot. It&#8217;s been my saving grace for constructing websites without having to write the code from scratch. But it&#8217;s gotten very, very bloated. I took a look at version 3.0 and the upcoming changes. It looks ok, but it worries me for the future. Now users actually expect updates and new features [...]]]></description>
			<content:encoded><![CDATA[<p>I like WordPress&#8211;a lot.  It&#8217;s been my saving grace for constructing websites without having to write the code from scratch.  But it&#8217;s gotten very, very bloated.  I took a look at version 3.0 and the upcoming changes.  It looks ok, but it <a href="http://human3rror.com/7-reasons-why-wordpress-could-fail-1/">worries me for the future</a>.  Now users actually <strong>expect</strong> updates and new features on a regular and frequent basis.&nbsp; Whatever happened to just wanting something that worked well, and was patched for bugs and security?&nbsp; I&#8217;m also worried about backward compatibility of things like themes and plugins.</p>
<p><span id="more-220"></span></p>
<p>Part of the reason I like WordPress is because it&#8217;s written very well compared to most open source LAMP products that came before it.&nbsp; It has a plugin and theme API which is relatively simple to learn.&nbsp; I would prefer WordPress to focus on improving the robustness of the API, rather than adding new features.</p>
<p>Overall I&#8217;m fairly confident in WordPress&#8217; developers to keep things straight.&nbsp; I just hope they&#8217;re not making changes just to keep themselves relevant.</p>
]]></content:encoded>
			<wfw:commentRss>http://bertolli.org/wordpress-bloated/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress:  the World of GPL Violations</title>
		<link>http://bertolli.org/wordpress-world-gpl-violations</link>
		<comments>http://bertolli.org/wordpress-world-gpl-violations#comments</comments>
		<pubDate>Sat, 25 Apr 2009 17:16:18 +0000</pubDate>
		<dc:creator>Angelo</dc:creator>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://angelo.bitfreedom.com/?p=166</guid>
		<description><![CDATA[It seems that the world WordPress themes is chock full of questionable use of GPL code.  I really wonder if there is someone I can report this to.  Let me give an example.  There is a site that sells a &#8220;membership&#8221; to download their themes.  Great, always happy to see someone getting paid for their [...]]]></description>
			<content:encoded><![CDATA[<p>It seems that the world WordPress themes is chock full of questionable use of GPL code.  I really wonder if there is someone I can report this to.  Let me give an example.  There is a site that sells a &#8220;membership&#8221; to download their themes.  Great, always happy to see someone getting paid for their hard work.  But then I read about <a href="http://www.elegantthemes.com/terms.html">the license on this individual&#8217;s work</a>.  So just like so many other WordPress themes, it is questionable whether or not you can create a theme at all that isn&#8217;t under a GPL compatible license.  What was even more shocking was this bad English:<span id="more-166"></span></p>
<blockquote><p>I reserves the right to change or modify current Terms of Use with no prior notice.</p></blockquote>
<p>Sorry, but if you give me a copy with a particular license, you cannot change it.  Even if you write this blurb on your website.  But I guess it&#8217;s enough to intimidate most Web users.</p>
<p>And now, for the blatant GPL violation:</p>
<blockquote><p>Several themes also make use of TimThumb, a script created by<a href="http://www.darrenhoyt.com/2008/04/02/timthumb-php-script-released/"> Darren Hoyt</a>. This file, timthumb.php, is released under the GPL, and retains its respective license as mentioned in the file itself. This file is not governed by the above license, and can be redistributed under the rules of the <a href="http://www.gnu.org/copyleft/gpl.html">GPL</a>.</p></blockquote>
<p>Really?!  So now you&#8217;re actually going as far as to distribute GPL code along with your code, that your code depends on, and NOT put it under the GPL?  I really hope that Darren Hoyt gave you permission to do that.</p>
<p><strong>UPDATE:</strong> I just took a look at the script, and it&#8217;s now under an MIT license.  It still doesn&#8217;t excuse the behavior of someone who obviously believes or used it when it was under the GPL.</p>
<p><strong>Links</strong></p>
<ul>
<li><a href="http://gpl-violations.org/">http://gpl-violations.org/</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://bertolli.org/wordpress-world-gpl-violations/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
