<?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: Adobe, Mobile Flash Player, JavaScript, etc.</title>
	<atom:link href="http://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/</link>
	<description>Thoughts, rants, and even some code from the mind of Barney Boisvert.</description>
	<lastBuildDate>Thu, 11 Sep 2014 09:58:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alexander</title>
		<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/comment-page-1/#comment-284164</link>
		<dc:creator>Alexander</dc:creator>
		<pubDate>Tue, 15 Nov 2011 17:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/?p=1743#comment-284164</guid>
		<description>Well more or less in the long term your arguments are valid even if JavaScript  is inferior language to ActionScript it will triumph in browsers. Because it gets support from companies like Google constantly building better JavaScript engines. If Google decide that JavaScript is inferior then it will be in trouble. Or maybe they already have decided it (Dart). 

About Apple I think they want to have control over app store at any coast ! They want people buying apps not using web apps :]. I hope one day they wont be able to control the apps users are using. But I am sure they definitely wont like people using web apps versus app store apps and they will do something about it when time arrives :].</description>
		<content:encoded><![CDATA[<p>Well more or less in the long term your arguments are valid even if JavaScript  is inferior language to ActionScript it will triumph in browsers. Because it gets support from companies like Google constantly building better JavaScript engines. If Google decide that JavaScript is inferior then it will be in trouble. Or maybe they already have decided it (Dart). </p>
<p>About Apple I think they want to have control over app store at any coast ! They want people buying apps not using web apps :]. I hope one day they wont be able to control the apps users are using. But I am sure they definitely wont like people using web apps versus app store apps and they will do something about it when time arrives :].</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: barneyb</title>
		<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/comment-page-1/#comment-283716</link>
		<dc:creator>barneyb</dc:creator>
		<pubDate>Fri, 11 Nov 2011 17:51:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/?p=1743#comment-283716</guid>
		<description>Alexander,

No one wants Flex to be dead.  No one wants Flash to be dead.  That&#039;s not true, of course, but I personally don&#039;t.  The point is that the market has spoken and it says that Flash and Flex are no longer cutting edge.  They were best-of-breed when they were new, but they&#039;ve both been superseded.  Why they were superseded is a matter of debate, but I think we can all agree that Adobe has put fewer resources into Flash Player and Flex than the browser makers and JavaScript tooling providers have poured into their respective projects/products.

Don&#039;t get me wrong, I&#039;ve built a good number of Flash-based applications and several decent sized Flex apps, all of which would have been impossible with JavaScript at the time.  But even four years ago, I was already rewriting Flex apps in JavaScript because the performance was better, the environment was more functional, and the code more maintainable.  Certain parts (like FDS for paging down tens of thousands of records and sorting them client-side) remain Flex, but the application changed to JavaScript.  Which isn&#039;t to say it&#039;s all roses with JavaScript.  Debugging support is a huge boon with Flex and FlashBuilder Pro.  So is compile-type typechecking.  But the dependency on DisplayObject, the very slow release cycles, the closedness Adobe has maintained over the project, etc. all make it an inferior choice even with it&#039;s huge selling points.

The Steve Jobs thing is a completely business-related issue, nothing to do with development.  He didn&#039;t care about the development experience, he cared about the user experience.  In his mind, making developers work twice as hard to give users a 10% better experience is a reasonable trade off.  His argument against Flash was about speed of the UI and compute power needed to run it, both of which are sound.  Flash Player was about control over the user experience.  With Flash Player around, he wouldn&#039;t be able to control the apps which were deployed and ensure they met the high expectations for Apple-ecosystems products.  Again, a valid set of choices to make, but not one I&#039;m considering here.  If Apple&#039;s refusal to allow Flash Player on iOS devices was the determining factor in Adobe abandoning Moible Flash Player they&#039;d have done it 3-4 years ago, not hung on until now.</description>
		<content:encoded><![CDATA[<p>Alexander,</p>
<p>No one wants Flex to be dead.  No one wants Flash to be dead.  That's not true, of course, but I personally don't.  The point is that the market has spoken and it says that Flash and Flex are no longer cutting edge.  They were best-of-breed when they were new, but they've both been superseded.  Why they were superseded is a matter of debate, but I think we can all agree that Adobe has put fewer resources into Flash Player and Flex than the browser makers and JavaScript tooling providers have poured into their respective projects/products.</p>
<p>Don't get me wrong, I've built a good number of Flash-based applications and several decent sized Flex apps, all of which would have been impossible with JavaScript at the time.  But even four years ago, I was already rewriting Flex apps in JavaScript because the performance was better, the environment was more functional, and the code more maintainable.  Certain parts (like FDS for paging down tens of thousands of records and sorting them client-side) remain Flex, but the application changed to JavaScript.  Which isn't to say it's all roses with JavaScript.  Debugging support is a huge boon with Flex and FlashBuilder Pro.  So is compile-type typechecking.  But the dependency on DisplayObject, the very slow release cycles, the closedness Adobe has maintained over the project, etc. all make it an inferior choice even with it's huge selling points.</p>
<p>The Steve Jobs thing is a completely business-related issue, nothing to do with development.  He didn't care about the development experience, he cared about the user experience.  In his mind, making developers work twice as hard to give users a 10% better experience is a reasonable trade off.  His argument against Flash was about speed of the UI and compute power needed to run it, both of which are sound.  Flash Player was about control over the user experience.  With Flash Player around, he wouldn't be able to control the apps which were deployed and ensure they met the high expectations for Apple-ecosystems products.  Again, a valid set of choices to make, but not one I'm considering here.  If Apple's refusal to allow Flash Player on iOS devices was the determining factor in Adobe abandoning Moible Flash Player they'd have done it 3-4 years ago, not hung on until now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander</title>
		<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/comment-page-1/#comment-283690</link>
		<dc:creator>Alexander</dc:creator>
		<pubDate>Fri, 11 Nov 2011 09:52:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/?p=1743#comment-283690</guid>
		<description>I am a web developer working with JavaScript and Flex. What I don&#039;t get really is why the people not working with Flash/Flex are so afraid of it, hate it and want it so badly to be dead :]. Even Jobs was afraid of flash getting on iOS devices because maybe the plugins can give similar user experience and people wont buy apps and he wont get his 30 %. 
It is sad that people are afraid and unite to kill a technology just because it is better then what they have now :\. I don&#039;t see any problem in keeping flash as the cutting edge tool to make stuff which will be available in HTML after 2-3 years.</description>
		<content:encoded><![CDATA[<p>I am a web developer working with JavaScript and Flex. What I don't get really is why the people not working with Flash/Flex are so afraid of it, hate it and want it so badly to be dead :]. Even Jobs was afraid of flash getting on iOS devices because maybe the plugins can give similar user experience and people wont buy apps and he wont get his 30 %.<br />
It is sad that people are afraid and unite to kill a technology just because it is better then what they have now :\. I don't see any problem in keeping flash as the cutting edge tool to make stuff which will be available in HTML after 2-3 years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devin</title>
		<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/comment-page-1/#comment-283675</link>
		<dc:creator>Devin</dc:creator>
		<pubDate>Fri, 11 Nov 2011 06:32:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/?p=1743#comment-283675</guid>
		<description>um, I don&#039;t think I&#039;ve ever seen a web development posting that didn&#039;t mention HTML regardless of what the primary technology was.  Way to be smart Josh.

But seriously... CF developers talking about &quot;other&quot; languages as dead? That&#039;s hilarious!</description>
		<content:encoded><![CDATA[<p>um, I don't think I've ever seen a web development posting that didn't mention HTML regardless of what the primary technology was.  Way to be smart Josh.</p>
<p>But seriously&#8230; CF developers talking about "other" languages as dead? That's hilarious!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Frankamp</title>
		<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/comment-page-1/#comment-283674</link>
		<dc:creator>Joshua Frankamp</dc:creator>
		<pubDate>Fri, 11 Nov 2011 06:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/?p=1743#comment-283674</guid>
		<description>Wow!

I thought the comments would be a bunch of boring amen&#039;s but here we have two people who actually choked on the idea that Flex is dead?

A rudimentary search shows 325 jobs with html and 49 with flex on Portland&#039;s craigslist. Now you must understand that most of those flex&#039;s don&#039;t count due to the words &quot;flex pay, flexible, flex your muscles&quot; etc. The HTML results all do count due to its wonderful uniqueness.

There are a few positions left with real Flex among them as requirements, most are optional with HTML as an alternative.

I believe Barney meant Flex is dead like IE 6 is dead. It was dead, and then died a very slow and painful death. It doesn&#039;t mean it isn&#039;t still taking up market share http://micgadget.com/11633/why-the-chinese-still-favour-internet-explorer-6/.

Adobe  has no qualms about jumping ship, it is smart business; don&#039;t be the last on board.</description>
		<content:encoded><![CDATA[<p>Wow!</p>
<p>I thought the comments would be a bunch of boring amen's but here we have two people who actually choked on the idea that Flex is dead?</p>
<p>A rudimentary search shows 325 jobs with html and 49 with flex on Portland's craigslist. Now you must understand that most of those flex's don't count due to the words "flex pay, flexible, flex your muscles" etc. The HTML results all do count due to its wonderful uniqueness.</p>
<p>There are a few positions left with real Flex among them as requirements, most are optional with HTML as an alternative.</p>
<p>I believe Barney meant Flex is dead like IE 6 is dead. It was dead, and then died a very slow and painful death. It doesn't mean it isn't still taking up market share <a href="http://micgadget.com/11633/why-the-chinese-still-favour-internet-explorer-6/" rel="nofollow">http://micgadget.com/11633/why-the-chinese-still-favour-internet-explorer-6/</a>.</p>
<p>Adobe  has no qualms about jumping ship, it is smart business; don't be the last on board.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: barneyb</title>
		<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/comment-page-1/#comment-283634</link>
		<dc:creator>barneyb</dc:creator>
		<pubDate>Thu, 10 Nov 2011 21:52:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/?p=1743#comment-283634</guid>
		<description>Devin,

You&#039;ll note I didn&#039;t say it isn&#039;t used.  However, the amount of resources pouring into moving the framework forward (let alone fixing the brokenness inside) is tiny compared to what is pushing comparable browser-technology-based frameworks forward.  When Flex came out it was best of breed, so a lot of people started using it.  Of course, the bar was quite low at that point.  The bar is a lot higher now, but there is still huge momentum behind Flex, so it will continue to be used for quite some time.

That said, from a long-term perspective, Flex was pretty much DOA.  It was based on a technology (Flash) which was already on the way down, and the implementation was lackluster to say the least.  Adobe had the ability to take their existing Flash platform and wrap it with a bunch of &quot;pretty developer stuff&quot; and capture an emerging market, but they didn&#039;t try to build a stellar platform, they just went for the market.  Which is totally legit, I might add.  But when you grab that market share, then you have to evolve into something which can keep it, and they haven&#039;t done that (and would have had trouble trying due their binding to the underlying Flash stuff).</description>
		<content:encoded><![CDATA[<p>Devin,</p>
<p>You'll note I didn't say it isn't used.  However, the amount of resources pouring into moving the framework forward (let alone fixing the brokenness inside) is tiny compared to what is pushing comparable browser-technology-based frameworks forward.  When Flex came out it was best of breed, so a lot of people started using it.  Of course, the bar was quite low at that point.  The bar is a lot higher now, but there is still huge momentum behind Flex, so it will continue to be used for quite some time.</p>
<p>That said, from a long-term perspective, Flex was pretty much DOA.  It was based on a technology (Flash) which was already on the way down, and the implementation was lackluster to say the least.  Adobe had the ability to take their existing Flash platform and wrap it with a bunch of "pretty developer stuff" and capture an emerging market, but they didn't try to build a stellar platform, they just went for the market.  Which is totally legit, I might add.  But when you grab that market share, then you have to evolve into something which can keep it, and they haven't done that (and would have had trouble trying due their binding to the underlying Flash stuff).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor M.</title>
		<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/comment-page-1/#comment-283633</link>
		<dc:creator>Victor M.</dc:creator>
		<pubDate>Thu, 10 Nov 2011 21:40:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/?p=1743#comment-283633</guid>
		<description>I read until the &quot;Flex died...&quot; sentence.

You have no clue.</description>
		<content:encoded><![CDATA[<p>I read until the "Flex died&#8230;" sentence.</p>
<p>You have no clue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devin</title>
		<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/comment-page-1/#comment-283631</link>
		<dc:creator>Devin</dc:creator>
		<pubDate>Thu, 10 Nov 2011 21:33:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/?p=1743#comment-283631</guid>
		<description>&quot;Flex died as a web application framework pretty much before it was released.  Which isn&#039;t to say it wasn&#039;t used (it was and still is), but the browser RIA juggernaut crushed it like a bug.&quot;

Really? Flex died that long ago? I&#039;ve been nothing but a Flex contractor for the last 6 years, and it&#039;s done nothing but grow and pop up in more and more places each year. I come across more Flex positions and offers in a single year than I ever did during my entire 8 year CF developer run combined. Heck, as I look through Dice for my metro area, there&#039;s probably 5 Flex positions for every 1 HTML5 position.</description>
		<content:encoded><![CDATA[<p>"Flex died as a web application framework pretty much before it was released.  Which isn't to say it wasn't used (it was and still is), but the browser RIA juggernaut crushed it like a bug."</p>
<p>Really? Flex died that long ago? I've been nothing but a Flex contractor for the last 6 years, and it's done nothing but grow and pop up in more and more places each year. I come across more Flex positions and offers in a single year than I ever did during my entire 8 year CF developer run combined. Heck, as I look through Dice for my metro area, there's probably 5 Flex positions for every 1 HTML5 position.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Brooks-Bilson</title>
		<link>https://www.barneyb.com/barneyblog/2011/11/10/adobe-mobile-flash-player-javascript-etc/comment-page-1/#comment-283619</link>
		<dc:creator>Rob Brooks-Bilson</dc:creator>
		<pubDate>Thu, 10 Nov 2011 19:31:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/?p=1743#comment-283619</guid>
		<description>Barney,

This pretty much echoes my thoughts on the subject as well. 

-Rob</description>
		<content:encoded><![CDATA[<p>Barney,</p>
<p>This pretty much echoes my thoughts on the subject as well. </p>
<p>-Rob</p>
]]></content:encoded>
	</item>
</channel>
</rss>
