
<?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: Zend Framework 1.6RC</title>
	<atom:link href="http://www.offshootinc.com/blog/2008/07/25/zend-framework-16rc/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.offshootinc.com/blog/2008/07/25/zend-framework-16rc/</link>
	<description>We build, mobilise and empower communities</description>
	<lastBuildDate>Thu, 02 Sep 2010 23:21:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Lasse</title>
		<link>http://www.offshootinc.com/blog/2008/07/25/zend-framework-16rc/comment-page-1/#comment-1246</link>
		<dc:creator>Lasse</dc:creator>
		<pubDate>Wed, 13 Aug 2008 18:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshootinc.com/blog/?p=124#comment-1246</guid>
		<description>I don&#039;t agree with your assessment. I think that Dojo is an excellent Framework to work with and I&#039;m happy to see it integrated with the Zend Framework.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t agree with your assessment. I think that Dojo is an excellent Framework to work with and I&#8217;m happy to see it integrated with the Zend Framework.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Woodford</title>
		<link>http://www.offshootinc.com/blog/2008/07/25/zend-framework-16rc/comment-page-1/#comment-1242</link>
		<dc:creator>Chris Woodford</dc:creator>
		<pubDate>Tue, 29 Jul 2008 20:23:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshootinc.com/blog/?p=124#comment-1242</guid>
		<description>Wil,

Thanks for you comment! Your explanation has cleared it up for me and allayed my fears.

I can definitely see what you&#039;re saying with points 2) - 4). Point 1) is a slight shocker, in that I&#039;m surprised that other frameworks would limit their redistribution. Maybe in the end the true influence of business is found in licensing and CLA policies. I don&#039;t really see why would so-called open source libraries limit their potential redistribution. The politics of business and programming will always baffle (and annoy) me. 

On the whole I do think it is a good idea that ZF is moving forward and offering integration with javascript libraries. (I just tend to be of the disposition to get all worked up when I suspect that business is interfering with open source :). The ZF/Dojo collaboration is likely only to make each product stronger.  However, I do hope the community will take Matthew&#039;s blueprint as an example and roll with it. 

So far I&#039;m loving the 1.6RC. ZF continues to get better and better with each release. Keep up the great work!

-chris</description>
		<content:encoded><![CDATA[<p>Wil,</p>
<p>Thanks for you comment! Your explanation has cleared it up for me and allayed my fears.</p>
<p>I can definitely see what you&#8217;re saying with points 2) &#8211; 4). Point 1) is a slight shocker, in that I&#8217;m surprised that other frameworks would limit their redistribution. Maybe in the end the true influence of business is found in licensing and CLA policies. I don&#8217;t really see why would so-called open source libraries limit their potential redistribution. The politics of business and programming will always baffle (and annoy) me. </p>
<p>On the whole I do think it is a good idea that ZF is moving forward and offering integration with javascript libraries. (I just tend to be of the disposition to get all worked up when I suspect that business is interfering with open source <img src='http://www.offshootinc.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . The ZF/Dojo collaboration is likely only to make each product stronger.  However, I do hope the community will take Matthew&#8217;s blueprint as an example and roll with it. </p>
<p>So far I&#8217;m loving the 1.6RC. ZF continues to get better and better with each release. Keep up the great work!</p>
<p>-chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wil Sinclair</title>
		<link>http://www.offshootinc.com/blog/2008/07/25/zend-framework-16rc/comment-page-1/#comment-1241</link>
		<dc:creator>Wil Sinclair</dc:creator>
		<pubDate>Fri, 25 Jul 2008 23:52:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshootinc.com/blog/?p=124#comment-1241</guid>
		<description>Well, I hope I can shed a bit more light on our decision process. First off, Zend tries to take our users desires in to account for all of our decisions. Ultimately, however, Zend has to decide where it will contribute just like any other contributor. We decided to contribute Dojo support for 4 basic reasons:

1) Their licensing and CLA policy is *very* similar to our and was one of the very few that would allow us to redistribute their libs in any of our distributions.
2) We wanted to work with a JavaScript toolkit project, as opposed to simply consuming it. The Dojo Foundation has been an excellent partner that we&#039;d been working with for months before announcing our decision.
3) We evaluated the most popular JS toolkits and concluded that Dojo best reflected the philosophy and MO of ZF.
4) While not the favorite of all ZF users, Dojo is one of the more popular frameworks in our community.

But I really must emphasize that this relationship is hardly exclusive on both sides. We hope that our community will step up with support for many JS toolkits such as JQuery, extJS, etc., and Matthew has mentioned that he designed the Dojo integration components such that they would serve well as a blueprint for other integrations.
Bottom line, Zend doesn&#039;t have a lot of resources to throw at ZF. We have to pick and choose where we put our own efforts. In the AJAX world we had to pick one horse, and after a lengthy evaluation we picked Dojo. We hope that you see as much value in Dojo as we do, but we also hope that in time you have the option of choosing another if Dojo&#039;s not the right toolkit for you.

In any case, I hope you enjoy ZF 1.6 and keep the feedback coming!
,Wil</description>
		<content:encoded><![CDATA[<p>Well, I hope I can shed a bit more light on our decision process. First off, Zend tries to take our users desires in to account for all of our decisions. Ultimately, however, Zend has to decide where it will contribute just like any other contributor. We decided to contribute Dojo support for 4 basic reasons:</p>
<p>1) Their licensing and CLA policy is *very* similar to our and was one of the very few that would allow us to redistribute their libs in any of our distributions.<br />
2) We wanted to work with a JavaScript toolkit project, as opposed to simply consuming it. The Dojo Foundation has been an excellent partner that we&#8217;d been working with for months before announcing our decision.<br />
3) We evaluated the most popular JS toolkits and concluded that Dojo best reflected the philosophy and MO of ZF.<br />
4) While not the favorite of all ZF users, Dojo is one of the more popular frameworks in our community.</p>
<p>But I really must emphasize that this relationship is hardly exclusive on both sides. We hope that our community will step up with support for many JS toolkits such as JQuery, extJS, etc., and Matthew has mentioned that he designed the Dojo integration components such that they would serve well as a blueprint for other integrations.<br />
Bottom line, Zend doesn&#8217;t have a lot of resources to throw at ZF. We have to pick and choose where we put our own efforts. In the AJAX world we had to pick one horse, and after a lengthy evaluation we picked Dojo. We hope that you see as much value in Dojo as we do, but we also hope that in time you have the option of choosing another if Dojo&#8217;s not the right toolkit for you.</p>
<p>In any case, I hope you enjoy ZF 1.6 and keep the feedback coming!<br />
,Wil</p>
]]></content:encoded>
	</item>
</channel>
</rss>
