<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Making the case for ActionScript</title>
	<atom:link href="http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/</link>
	<description>Founding Partner - Project Cocoon</description>
	<lastBuildDate>Tue, 16 Mar 2010 15:57:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tariq Ahmed</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22870</link>
		<dc:creator>Tariq Ahmed</dc:creator>
		<pubDate>Thu, 03 Sep 2009 20:49:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22870</guid>
		<description>Interesting post!

I have a simple thing to note, and that is it&#039;s the hardcore powernerds that tend to be very vocal about things like language evolution, method and operator overloading, etc... 

And all that noise makes it sound like it&#039;s what everyone wants. However, it&#039;s the average joe that represents 80% of the coding population, and their voice is not represented.

I&#039;ve always been an advocate for catering towards making things easy for that kind of user.</description>
		<content:encoded><![CDATA[<p>Interesting post!</p>
<p>I have a simple thing to note, and that is it&#8217;s the hardcore powernerds that tend to be very vocal about things like language evolution, method and operator overloading, etc&#8230; </p>
<p>And all that noise makes it sound like it&#8217;s what everyone wants. However, it&#8217;s the average joe that represents 80% of the coding population, and their voice is not represented.</p>
<p>I&#8217;ve always been an advocate for catering towards making things easy for that kind of user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alain Raap</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22792</link>
		<dc:creator>Alain Raap</dc:creator>
		<pubDate>Wed, 26 Aug 2009 21:55:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22792</guid>
		<description>I was thinking of Lego, when Lego started to create  new boxes to build large structures (cars/trains/planes etc) which could move and were able to drive, move and turn around, a lot of kids didn&#039;t play with Lego anymore. 
Maybe we should return to the simple view of a kid who builds a house or a car with just a set of wheels and stones. All those frameworks and patters are great to build large applications, but it destructs creativity. Just my humble opinion.</description>
		<content:encoded><![CDATA[<p>I was thinking of Lego, when Lego started to create  new boxes to build large structures (cars/trains/planes etc) which could move and were able to drive, move and turn around, a lot of kids didn&#8217;t play with Lego anymore.<br />
Maybe we should return to the simple view of a kid who builds a house or a car with just a set of wheels and stones. All those frameworks and patters are great to build large applications, but it destructs creativity. Just my humble opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomsamson</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22529</link>
		<dc:creator>tomsamson</dc:creator>
		<pubDate>Fri, 14 Aug 2009 01:14:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22529</guid>
		<description>haha
http://go.internet.com/?id=474X1088&amp;url=http%3A%2F%2Fwww.dearadobe.com%2Ftop_rated_apps.php</description>
		<content:encoded><![CDATA[<p>haha<br />
<a href="http://go.internet.com/?id=474X1088&amp;url=http%3A%2F%2Fwww.dearadobe.com%2Ftop_rated_apps.php" rel="nofollow">http://go.internet.com/?id=474X1088&amp;url=http%3A%2F%2Fwww.dearadobe.com%2Ftop_rated_apps.php</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Redwoods</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22522</link>
		<dc:creator>Adam Redwoods</dc:creator>
		<pubDate>Thu, 13 Aug 2009 21:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22522</guid>
		<description>Thanks for writing this article and raising awareness to this deviation in Flash, Peter.

I strongly believe that AS3 and OOP was needed for developers to advance Flash, but should not have been done at the expense of the Flash authoring environment or basic actionscript.

As a freelance designer, I have been able to make quick, simple interfaces, but now with AS3 and the authoring environment forcing me to use it with new features, I find myself more and more alienated by the environment. In other words, programming takes longer, which sometimes forces me to outsource it thus upping my costs-- something I cannot always financially do.

If I have to outsource the programming, why not also consider AJAX, Silverlight, or something else? In this scenario, Flash loses its advantage.</description>
		<content:encoded><![CDATA[<p>Thanks for writing this article and raising awareness to this deviation in Flash, Peter.</p>
<p>I strongly believe that AS3 and OOP was needed for developers to advance Flash, but should not have been done at the expense of the Flash authoring environment or basic actionscript.</p>
<p>As a freelance designer, I have been able to make quick, simple interfaces, but now with AS3 and the authoring environment forcing me to use it with new features, I find myself more and more alienated by the environment. In other words, programming takes longer, which sometimes forces me to outsource it thus upping my costs&#8211; something I cannot always financially do.</p>
<p>If I have to outsource the programming, why not also consider AJAX, Silverlight, or something else? In this scenario, Flash loses its advantage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomsamson</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22482</link>
		<dc:creator>tomsamson</dc:creator>
		<pubDate>Wed, 12 Aug 2009 16:21:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22482</guid>
		<description>Delfield, you bring up an interesting view but some things you say are clearly off.
&quot;Though not designers, programmers are THE market&quot;

Really, isn´t that a very limited ignorant view?
The whole discussion here and elsewhere shows that very different kinds of people use flash platform tools, there is no single usertype and to say something as you do there is just wrong.

&quot;Likewise, most designers don’t know coding, and need a programmer to perform that task.&quot;

That is an antiquated view and a big part of the problem: Saying we now realized there are no designers who also can or want to get things done with code, it should be like in ages past where coders code and don´t touch art and designers lay out static designs in photoshop or flash or catalyst and coders add any kind of logic to that then.
Flash and other tools and languages of its time have evolved as being something that allows each group to do each and combine em, too.
Sure you might have a classic business where there are different types of coder groups, different kinds of artists and they touch each others work as few as possible, but in this day and age for most smaller- medium size teams that is probably less and less common. I know many big agencies where they have several flash cracks who basically do one flash project after the other on their own or in small teams of 2-5, including all art, code and sound side. To my experiece its also of clear advantage that someone has a good knowledgebase in each field so he has understandings for the hows and whys.
Sure someone who only spends his time in one field can maybe exceed in that field compared to someone else who does several different kinds of things but why force people to one field if they want to and could do several for many years?

In such areas i completely disagree with your posts, i think at the end of the day AS3 will get more refined, the flash player will get more refined, silverlight will get more refined just like html 5/ canvas stuff, unity etc and at the end people will use what feels like the best tool to get the job done for em.
For some performance might be more important, for others supported platforms, for others the usability of the tool and language that allows em to get more done in less time.
I think what the discussion shows is that the vibe of &quot;making the language more mature&quot; ( = copying java more ) has not exactly worked out for the popularity of the language and tools; allowing people to express themselves with filters, seamless video integration etc better and with more, easier and more flexible usability than contenders seems to work out better.
To end i´ll reply to this:
&quot;
You may sense the shift without being able to pinpoint it, but AS3 has given Adobe a larger market.
&quot;

Really? Maybe a potentially bigger market, but in reality it looks like the one release with AS3 aswell as ones following were among those worst selling ever (maybe only the one in which AS2 was introduced sold similarly bad).
I also see more flash platform developers than ever looking around if they maybe shouldn´t play around with unity, silverlight or html 5 stuff some more meanwhile.


If you want to make all happy you have to support and evolve AS1,2 and 3 or also other languages fully, allow to make full use of the API in all and use propper hardware acceleration with all automatically for all display operations so performance is good with each.
Otherwise, well, you´ll always have one group, maybe the bigger group hating on a new release and looking around to use other stuff.</description>
		<content:encoded><![CDATA[<p>Delfield, you bring up an interesting view but some things you say are clearly off.<br />
&#8220;Though not designers, programmers are THE market&#8221;</p>
<p>Really, isn´t that a very limited ignorant view?<br />
The whole discussion here and elsewhere shows that very different kinds of people use flash platform tools, there is no single usertype and to say something as you do there is just wrong.</p>
<p>&#8220;Likewise, most designers don’t know coding, and need a programmer to perform that task.&#8221;</p>
<p>That is an antiquated view and a big part of the problem: Saying we now realized there are no designers who also can or want to get things done with code, it should be like in ages past where coders code and don´t touch art and designers lay out static designs in photoshop or flash or catalyst and coders add any kind of logic to that then.<br />
Flash and other tools and languages of its time have evolved as being something that allows each group to do each and combine em, too.<br />
Sure you might have a classic business where there are different types of coder groups, different kinds of artists and they touch each others work as few as possible, but in this day and age for most smaller- medium size teams that is probably less and less common. I know many big agencies where they have several flash cracks who basically do one flash project after the other on their own or in small teams of 2-5, including all art, code and sound side. To my experiece its also of clear advantage that someone has a good knowledgebase in each field so he has understandings for the hows and whys.<br />
Sure someone who only spends his time in one field can maybe exceed in that field compared to someone else who does several different kinds of things but why force people to one field if they want to and could do several for many years?</p>
<p>In such areas i completely disagree with your posts, i think at the end of the day AS3 will get more refined, the flash player will get more refined, silverlight will get more refined just like html 5/ canvas stuff, unity etc and at the end people will use what feels like the best tool to get the job done for em.<br />
For some performance might be more important, for others supported platforms, for others the usability of the tool and language that allows em to get more done in less time.<br />
I think what the discussion shows is that the vibe of &#8220;making the language more mature&#8221; ( = copying java more ) has not exactly worked out for the popularity of the language and tools; allowing people to express themselves with filters, seamless video integration etc better and with more, easier and more flexible usability than contenders seems to work out better.<br />
To end i´ll reply to this:<br />
&#8221;<br />
You may sense the shift without being able to pinpoint it, but AS3 has given Adobe a larger market.<br />
&#8221;</p>
<p>Really? Maybe a potentially bigger market, but in reality it looks like the one release with AS3 aswell as ones following were among those worst selling ever (maybe only the one in which AS2 was introduced sold similarly bad).<br />
I also see more flash platform developers than ever looking around if they maybe shouldn´t play around with unity, silverlight or html 5 stuff some more meanwhile.</p>
<p>If you want to make all happy you have to support and evolve AS1,2 and 3 or also other languages fully, allow to make full use of the API in all and use propper hardware acceleration with all automatically for all display operations so performance is good with each.<br />
Otherwise, well, you´ll always have one group, maybe the bigger group hating on a new release and looking around to use other stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Delfeld</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22481</link>
		<dc:creator>Delfeld</dc:creator>
		<pubDate>Wed, 12 Aug 2009 15:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22481</guid>
		<description>I forgot to mention, with the goal of having all Adobe products using ActionScript by 2013, we cannot fairly judge the results from the middle.  Everything has to continue to work, but every version should be expected to be foreign to us in some substantial way, and we have to learn the new method (which is really the standard way of doing things outside of Adobe).</description>
		<content:encoded><![CDATA[<p>I forgot to mention, with the goal of having all Adobe products using ActionScript by 2013, we cannot fairly judge the results from the middle.  Everything has to continue to work, but every version should be expected to be foreign to us in some substantial way, and we have to learn the new method (which is really the standard way of doing things outside of Adobe).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Delfeld</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22480</link>
		<dc:creator>Delfeld</dc:creator>
		<pubDate>Wed, 12 Aug 2009 15:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22480</guid>
		<description>Peter,

  I think you are bifurcating the issue.  I coded in FlashMX, and because of that experience refused to use FlashMX.  The decision was made some time ago to step away from Macromedia&#039;s ad hoc programming and pursue a more formal programming language structure (an ECMA standard, too - actually, with Flex, there seems to be two standards).  Because of the work done in that direction, I have stopped bad-mouthing Flash.  

  Further, you have to consider the competition.  MS killed Adobe&#039;s &quot;Javascript 2.0&quot; initiative.  You have to ask yourself &quot;Why?&quot;.  It is not because MS thinks JS2 is a bad idea - just the opposite.  It is an extremely powerful idea, one which brings Adobe up to the level of real programming, makes it as extendible as MS&#039;s operating system, and, with Adobe&#039;s ubiquitous presence, allows Adobe to rule the market.  You will notice that Silverlight is OO, and is trying to market itself as a Flash substitute.  

  Adobe is not foolish on this point.  With AIR and the possibilities of platform independent desktop apps, you must have an extensible structure.  E.g., I would dread making an app in Perl.  OO is a structure that opens up the door to programmers.  Though not designers, programmers are THE market.  Look at it another way: Adobe could hold onto the &quot;designers only&quot; idea, but if MS and Google can give designers what they want AND give programmers what they want, then Adobe will not be staying &quot;pure&quot; to the creed by focusing on designers; rather, it will dissappear.  

  A long time ago, I learned C++ because I wanted to design 3D, and not knowing programming structure hindered me.  Likewise, most designers don&#039;t know coding, and need a programmer to perform that task.  But that is growth; when an idea gets big, tasks have to be divided.  Do you still want a barber to be your dentist?  It&#039;s that sort of thing.  There is a lot to know now because there are a lot of possibilities.  And you don&#039;t have to know everything.  Flash, Illustrator and Photoshop can be the realm of the graphics inclined.  But don&#039;t mistake this for creativity, nor the only goal.  

  You may sense the shift without being able to pinpoint it, but AS3 has given Adobe a larger market.  This bigger workspace has more and different demands, so what it means for Adobe to be &quot;market driven&quot; is changing.  Focusing on the graphic side as a core (putting other things on the back burner) is no longer possible, because it is no longer reflecting what Adobe *is*.

  Peter, thank you for inspiring this discussion!  I have to admit that I would not have thought about much of this without reading your post, and the followup comments.</description>
		<content:encoded><![CDATA[<p>Peter,</p>
<p>  I think you are bifurcating the issue.  I coded in FlashMX, and because of that experience refused to use FlashMX.  The decision was made some time ago to step away from Macromedia&#8217;s ad hoc programming and pursue a more formal programming language structure (an ECMA standard, too &#8211; actually, with Flex, there seems to be two standards).  Because of the work done in that direction, I have stopped bad-mouthing Flash.  </p>
<p>  Further, you have to consider the competition.  MS killed Adobe&#8217;s &#8220;Javascript 2.0&#8243; initiative.  You have to ask yourself &#8220;Why?&#8221;.  It is not because MS thinks JS2 is a bad idea &#8211; just the opposite.  It is an extremely powerful idea, one which brings Adobe up to the level of real programming, makes it as extendible as MS&#8217;s operating system, and, with Adobe&#8217;s ubiquitous presence, allows Adobe to rule the market.  You will notice that Silverlight is OO, and is trying to market itself as a Flash substitute.  </p>
<p>  Adobe is not foolish on this point.  With AIR and the possibilities of platform independent desktop apps, you must have an extensible structure.  E.g., I would dread making an app in Perl.  OO is a structure that opens up the door to programmers.  Though not designers, programmers are THE market.  Look at it another way: Adobe could hold onto the &#8220;designers only&#8221; idea, but if MS and Google can give designers what they want AND give programmers what they want, then Adobe will not be staying &#8220;pure&#8221; to the creed by focusing on designers; rather, it will dissappear.  </p>
<p>  A long time ago, I learned C++ because I wanted to design 3D, and not knowing programming structure hindered me.  Likewise, most designers don&#8217;t know coding, and need a programmer to perform that task.  But that is growth; when an idea gets big, tasks have to be divided.  Do you still want a barber to be your dentist?  It&#8217;s that sort of thing.  There is a lot to know now because there are a lot of possibilities.  And you don&#8217;t have to know everything.  Flash, Illustrator and Photoshop can be the realm of the graphics inclined.  But don&#8217;t mistake this for creativity, nor the only goal.  </p>
<p>  You may sense the shift without being able to pinpoint it, but AS3 has given Adobe a larger market.  This bigger workspace has more and different demands, so what it means for Adobe to be &#8220;market driven&#8221; is changing.  Focusing on the graphic side as a core (putting other things on the back burner) is no longer possible, because it is no longer reflecting what Adobe *is*.</p>
<p>  Peter, thank you for inspiring this discussion!  I have to admit that I would not have thought about much of this without reading your post, and the followup comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Anderson&#8217;s ITWriting - Tech writing blog &#187; Where next for Adobe ActionScript?</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22473</link>
		<dc:creator>Tim Anderson&#8217;s ITWriting - Tech writing blog &#187; Where next for Adobe ActionScript?</dc:creator>
		<pubDate>Wed, 12 Aug 2009 08:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22473</guid>
		<description>[...] amazing Alchemy (which compiles C/C++ to ActionScript) to be available to all ActionScript code. Peter Elst asks for ActionScript to be decoupled from the player and replaced with a dynamic language [...]</description>
		<content:encoded><![CDATA[<p>[...] amazing Alchemy (which compiles C/C++ to ActionScript) to be available to all ActionScript code. Peter Elst asks for ActionScript to be decoupled from the player and replaced with a dynamic language [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arby</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22471</link>
		<dc:creator>Arby</dc:creator>
		<pubDate>Tue, 11 Aug 2009 21:05:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22471</guid>
		<description>&quot;This also opens up opportunities for a formal plugin architecture allowing you to ‘decorate’ the Flash Player with additional functionality. &quot;
oh god, I hope you dont mean &quot;plugins&quot; or DLLs! Remember the hell it was to use Shockwave and stay on top of the hundreds of plugins available for it... BLEAH!

As an AS2 coder though I want to stick my nose in here and say that I want the AS3 speed, AS3 timeline benefits, but I don&#039;t want all this complicated &quot;developer&quot; crap that is AS3.  WHY NOT keep it simple like .onClick ? Why add all this extra crap defining it as a mouse event, etc? What ELSE will it be? What ELSE can CLICK on a button other than a MOUSE POINTER?!

Same for getting a URL. Sheesh. Here&#039;s the address, Open it in THIS window. Simple as that.

I really hate having to GUESS at what libraries need importing too. Why can&#039;t Flash just tell me, hey, the class is missing, you need to import THIS and then do it for me?</description>
		<content:encoded><![CDATA[<p>&#8220;This also opens up opportunities for a formal plugin architecture allowing you to ‘decorate’ the Flash Player with additional functionality. &#8221;<br />
oh god, I hope you dont mean &#8220;plugins&#8221; or DLLs! Remember the hell it was to use Shockwave and stay on top of the hundreds of plugins available for it&#8230; BLEAH!</p>
<p>As an AS2 coder though I want to stick my nose in here and say that I want the AS3 speed, AS3 timeline benefits, but I don&#8217;t want all this complicated &#8220;developer&#8221; crap that is AS3.  WHY NOT keep it simple like .onClick ? Why add all this extra crap defining it as a mouse event, etc? What ELSE will it be? What ELSE can CLICK on a button other than a MOUSE POINTER?!</p>
<p>Same for getting a URL. Sheesh. Here&#8217;s the address, Open it in THIS window. Simple as that.</p>
<p>I really hate having to GUESS at what libraries need importing too. Why can&#8217;t Flash just tell me, hey, the class is missing, you need to import THIS and then do it for me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ReactionScript3 &#124; Hot Trends 2 Tweet</title>
		<link>http://www.peterelst.com/blog/2009/08/09/making-the-case-for-actionscript/comment-page-2/#comment-22468</link>
		<dc:creator>ReactionScript3 &#124; Hot Trends 2 Tweet</dc:creator>
		<pubDate>Tue, 11 Aug 2009 11:28:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=2337#comment-22468</guid>
		<description>[...] Making the Case for ActionScript by Peter Elst [...]</description>
		<content:encoded><![CDATA[<p>[...] Making the Case for ActionScript by Peter Elst [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
