<?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: Why can&#8217;t Flex get into the CS Party?</title>
	<atom:link href="http://www.valhead.com/2008/11/06/why-cant-flex-get-into-the-cs-party/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.valhead.com/2008/11/06/why-cant-flex-get-into-the-cs-party/</link>
	<description>....</description>
	<lastBuildDate>Sat, 31 Dec 2011 03:45:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Matthew Fabb</title>
		<link>http://www.valhead.com/2008/11/06/why-cant-flex-get-into-the-cs-party/comment-page-1/#comment-431</link>
		<dc:creator>Matthew Fabb</dc:creator>
		<pubDate>Fri, 07 Nov 2008 17:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.valhead.com/blog/?p=92#comment-431</guid>
		<description>I definitely think it has to do with release cycles more than anything else.

The match up the release cycles, Flex Builder 4 would have to be delayed to be released with CS5. Or following Flex Builder 4, we would have a small increment release (version 4.1? 4.5?) to go along with CS5 and then have to wait longer than we should for Flex Builder 5. Neither option makes much business sense.

Plus with the upcoming Thermo likely to be released together with Flex Builder 4, Adobe will have now 2 products in a different release cycle. Which also from a business side of things makes more sense rather than Adobe&#039;s revenue going up and down based on the CS release cycle, have two major products spaced out. Perhaps pull off Dreamweaver and add it to Flex Builder and Thermo for a separate DS (Developer Suite)?</description>
		<content:encoded><![CDATA[<p>I definitely think it has to do with release cycles more than anything else.</p>
<p>The match up the release cycles, Flex Builder 4 would have to be delayed to be released with CS5. Or following Flex Builder 4, we would have a small increment release (version 4.1? 4.5?) to go along with CS5 and then have to wait longer than we should for Flex Builder 5. Neither option makes much business sense.</p>
<p>Plus with the upcoming Thermo likely to be released together with Flex Builder 4, Adobe will have now 2 products in a different release cycle. Which also from a business side of things makes more sense rather than Adobe&#8217;s revenue going up and down based on the CS release cycle, have two major products spaced out. Perhaps pull off Dreamweaver and add it to Flex Builder and Thermo for a separate DS (Developer Suite)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ethan Estes</title>
		<link>http://www.valhead.com/2008/11/06/why-cant-flex-get-into-the-cs-party/comment-page-1/#comment-430</link>
		<dc:creator>Ethan Estes</dc:creator>
		<pubDate>Fri, 07 Nov 2008 15:55:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.valhead.com/blog/?p=92#comment-430</guid>
		<description>I think an issue is that their development cycles are one half off-so each release comes half way through the other. Very hard to work in the integration across the suite when you&#039;ve built on eclipse and it&#039;s release schedule. Not impossible but not the same when you write it from scratch and own all the code.</description>
		<content:encoded><![CDATA[<p>I think an issue is that their development cycles are one half off-so each release comes half way through the other. Very hard to work in the integration across the suite when you&#8217;ve built on eclipse and it&#8217;s release schedule. Not impossible but not the same when you write it from scratch and own all the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://www.valhead.com/2008/11/06/why-cant-flex-get-into-the-cs-party/comment-page-1/#comment-429</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Fri, 07 Nov 2008 15:47:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.valhead.com/blog/?p=92#comment-429</guid>
		<description>My guess is that it&#039;s not really necessary to include it in a paid product like CS.
Flex is free to download and Flex Builder is just Eclipse sans Java.  I used to use Flex Builder, but now I use Zend Studio with the Flex Plugin and all the functionality is the same.

As far as an IDE for Actionscript, Textmate is truly incredible. My IDEs used to be Flash / Flex Builder, now it&#039;s Flash, Zend, and Textmate.  Look into it.</description>
		<content:encoded><![CDATA[<p>My guess is that it&#8217;s not really necessary to include it in a paid product like CS.<br />
Flex is free to download and Flex Builder is just Eclipse sans Java.  I used to use Flex Builder, but now I use Zend Studio with the Flex Plugin and all the functionality is the same.</p>
<p>As far as an IDE for Actionscript, Textmate is truly incredible. My IDEs used to be Flash / Flex Builder, now it&#8217;s Flash, Zend, and Textmate.  Look into it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: val</title>
		<link>http://www.valhead.com/2008/11/06/why-cant-flex-get-into-the-cs-party/comment-page-1/#comment-428</link>
		<dc:creator>val</dc:creator>
		<pubDate>Fri, 07 Nov 2008 13:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.valhead.com/blog/?p=92#comment-428</guid>
		<description>Good point Adrian, I didn&#039;t think of that. Might be part of the reason for sure. 

and yes, hopefully by CS5 there&#039;s some better workflow built in for all us designer/developer folks!</description>
		<content:encoded><![CDATA[<p>Good point Adrian, I didn&#8217;t think of that. Might be part of the reason for sure. </p>
<p>and yes, hopefully by CS5 there&#8217;s some better workflow built in for all us designer/developer folks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://www.valhead.com/2008/11/06/why-cant-flex-get-into-the-cs-party/comment-page-1/#comment-427</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Fri, 07 Nov 2008 10:52:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.valhead.com/blog/?p=92#comment-427</guid>
		<description>Programmers aren&#039;t invited to creative parties ;)

But now a bit more serious:

Maybe because its based on eclipse not developed by Adobe. And eclipse is no proprietary software - the others in the CS Party are. So nobody invites it :D</description>
		<content:encoded><![CDATA[<p>Programmers aren&#8217;t invited to creative parties <img src='http://www.valhead.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>But now a bit more serious:</p>
<p>Maybe because its based on eclipse not developed by Adobe. And eclipse is no proprietary software &#8211; the others in the CS Party are. So nobody invites it <img src='http://www.valhead.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iain</title>
		<link>http://www.valhead.com/2008/11/06/why-cant-flex-get-into-the-cs-party/comment-page-1/#comment-426</link>
		<dc:creator>Iain</dc:creator>
		<pubDate>Fri, 07 Nov 2008 10:08:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.valhead.com/blog/?p=92#comment-426</guid>
		<description>I guess one reason is that the Thermo features are still in development, so wouldn&#039;t have been ready. Maybe in CS 5?</description>
		<content:encoded><![CDATA[<p>I guess one reason is that the Thermo features are still in development, so wouldn&#8217;t have been ready. Maybe in CS 5?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

