<?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: An Adobe Flash developer on why the iPad can&#8217;t use Flash</title>
	<atom:link href="http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/</link>
	<description>Daniel Eran Dilger in San Francisco</description>
	<lastBuildDate>Sat, 04 Sep 2010 14:10:49 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MinuteWalt</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-31561</link>
		<dc:creator>MinuteWalt</dc:creator>
		<pubDate>Wed, 18 Aug 2010 06:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-31561</guid>
		<description>Morgan does not make a compelling argument as to why Apple and Flash don&#039;t mix. It is, however, a great argument that touch-screen UIs don&#039;t mix with applications designed for mouses and keyboards. 

All of Morgan&#039;s points focus around UI, and that has nothing to do with what&#039;s currently happening with the whole Flash/Apple hissy fit.

I currently have a all-in-one PC with a touch screen, and for kicks, I tried a bunch of different things totally mouse-free tonight. (I don&#039;t think I&#039;ve actually tried to use the touch-screen much before tonight in fact! I&#039;ve got a mouse and a full keyboard, &amp; the concept of having a touch-screen when you have a keyboard and a mouse RIGHT THERE in front of you frankly baffled me, but this is what they gave me for an RMI&#039;d hardware failure replacement for my old system.)

The results were mixed: I was able to watch Flash-based media sites and navigate most other websites just dandy, but games and applications were between &quot;meh&quot; and &quot;unworkable.&quot;

That&#039;s it.  Whoo-hoo.

Using a touch UI didn&#039;t totally kill the content that I can&#039;t (currently) get on my mobile device. In most cases, it didn&#039;t affect it at all (Hulu, Ze Frank, and many others that are based on Flash). In some, not even related to Flash, it just made things weird (copy-and-paste vs. scrolling: which on would you give up?) In some cases (mostly games, Flash and not-Flash), touching was simply unviable.

And that&#039;s OK with me.

I understand that using a mobile will not give me the same experience. Users of mobile devices don&#039;t care: we KNOW that we&#039;re not getting 100% of a website, because we&#039;re holding a phone or tablet in our hands instead of a keyboard and monitor that has to sit on a table or on our laps.

So, the UI argument is kind of semi-valid. 

Yeah, mouse-over vs. click does something important, but not all that important. Most applications don&#039;t need it, many are slightly less functional without it. Some applications that are made for things-that-are-not-phones-or-tablets, would be completely crippled by the UI issue. And these are applications like word processors and video games that you&#039;d probably want to access on your desktop anyway, because the UI is better.

What it boils down to is this: 

I can&#039;t access a huge portion of the internet from my portable device. I&#039;d be OK with some kind of broken access; it&#039;s better than no access at all. Broken access is what you get with a portable device anyway. It&#039;s expected that a 4x2 handheld won&#039;t give you the same experience of a desktop.

Garbage-y Flash games have brought my tower to a standstill on many occasions, and would probably do the same thing to my phone. This happened tonight, in fact, and I had to use Task Manager to kill my browser more than once. But many phone apps have decided that they needed my phone&#039;s resources more than, say, my ability to call people. That&#039;s just bad programming, and has little to do with the runtime that it was built on.

So I gotta say, mousing habits won&#039;t affect most users&#039; experiences beyond what what we have to get used to when switching from a desktop to a portable touchscreen device. UI conflicts are important, but they don&#039;t really break the user experience at this point. 

spoken from the viewpoint of a user who has used touch UI to experience non-portable developed content</description>
		<content:encoded><![CDATA[<p>Morgan does not make a compelling argument as to why Apple and Flash don&#8217;t mix. It is, however, a great argument that touch-screen UIs don&#8217;t mix with applications designed for mouses and keyboards. </p>
<p>All of Morgan&#8217;s points focus around UI, and that has nothing to do with what&#8217;s currently happening with the whole Flash/Apple hissy fit.</p>
<p>I currently have a all-in-one PC with a touch screen, and for kicks, I tried a bunch of different things totally mouse-free tonight. (I don&#8217;t think I&#8217;ve actually tried to use the touch-screen much before tonight in fact! I&#8217;ve got a mouse and a full keyboard, &amp; the concept of having a touch-screen when you have a keyboard and a mouse RIGHT THERE in front of you frankly baffled me, but this is what they gave me for an RMI&#8217;d hardware failure replacement for my old system.)</p>
<p>The results were mixed: I was able to watch Flash-based media sites and navigate most other websites just dandy, but games and applications were between &#8220;meh&#8221; and &#8220;unworkable.&#8221;</p>
<p>That&#8217;s it.  Whoo-hoo.</p>
<p>Using a touch UI didn&#8217;t totally kill the content that I can&#8217;t (currently) get on my mobile device. In most cases, it didn&#8217;t affect it at all (Hulu, Ze Frank, and many others that are based on Flash). In some, not even related to Flash, it just made things weird (copy-and-paste vs. scrolling: which on would you give up?) In some cases (mostly games, Flash and not-Flash), touching was simply unviable.</p>
<p>And that&#8217;s OK with me.</p>
<p>I understand that using a mobile will not give me the same experience. Users of mobile devices don&#8217;t care: we KNOW that we&#8217;re not getting 100% of a website, because we&#8217;re holding a phone or tablet in our hands instead of a keyboard and monitor that has to sit on a table or on our laps.</p>
<p>So, the UI argument is kind of semi-valid. </p>
<p>Yeah, mouse-over vs. click does something important, but not all that important. Most applications don&#8217;t need it, many are slightly less functional without it. Some applications that are made for things-that-are-not-phones-or-tablets, would be completely crippled by the UI issue. And these are applications like word processors and video games that you&#8217;d probably want to access on your desktop anyway, because the UI is better.</p>
<p>What it boils down to is this: </p>
<p>I can&#8217;t access a huge portion of the internet from my portable device. I&#8217;d be OK with some kind of broken access; it&#8217;s better than no access at all. Broken access is what you get with a portable device anyway. It&#8217;s expected that a 4&#215;2 handheld won&#8217;t give you the same experience of a desktop.</p>
<p>Garbage-y Flash games have brought my tower to a standstill on many occasions, and would probably do the same thing to my phone. This happened tonight, in fact, and I had to use Task Manager to kill my browser more than once. But many phone apps have decided that they needed my phone&#8217;s resources more than, say, my ability to call people. That&#8217;s just bad programming, and has little to do with the runtime that it was built on.</p>
<p>So I gotta say, mousing habits won&#8217;t affect most users&#8217; experiences beyond what what we have to get used to when switching from a desktop to a portable touchscreen device. UI conflicts are important, but they don&#8217;t really break the user experience at this point. </p>
<p>spoken from the viewpoint of a user who has used touch UI to experience non-portable developed content</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheCosmonaut</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-28005</link>
		<dc:creator>TheCosmonaut</dc:creator>
		<pubDate>Tue, 18 May 2010 04:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-28005</guid>
		<description>@Dan J
LOL - well, I guess you should have written THAT article instead of the one you did. :)

Can you look beyond your knee-jerk reactions to see that I&#039;m not arguing that Flash is awesome? I&#039;m just saying this: This post argues that Flash CAN&#039;T work on gestural devices because rollovers won&#039;t work. That argument is obviously wrong.

I&#039;m all for criticism of Adobe. I love my iPhone. I&#039;m all for getting rid of Flash in favor of open standards. jQuery is a beautiful thing. If I could program tomorrow in JavaScript and HTML5 what I can do today in Flash, I&#039;d do it in a heartbeat.

What I&#039;m not all for is people taking an illogical premise, presenting it as fact, ignoring all evidence to the contrary, and then attempting to introduce new points when their argument is refuted. If you want to label anyone as a supporter of &quot;grand design&quot; in this argument, I&#039;m afraid it&#039;s you, my friend.

You write good stuff. This is a well-run site. Everyone gets things wrong from time to time. It&#039;s OK! :D</description>
		<content:encoded><![CDATA[<p>@Dan J<br />
LOL &#8211; well, I guess you should have written THAT article instead of the one you did. :)</p>
<p>Can you look beyond your knee-jerk reactions to see that I&#8217;m not arguing that Flash is awesome? I&#8217;m just saying this: This post argues that Flash CAN&#8217;T work on gestural devices because rollovers won&#8217;t work. That argument is obviously wrong.</p>
<p>I&#8217;m all for criticism of Adobe. I love my iPhone. I&#8217;m all for getting rid of Flash in favor of open standards. jQuery is a beautiful thing. If I could program tomorrow in JavaScript and HTML5 what I can do today in Flash, I&#8217;d do it in a heartbeat.</p>
<p>What I&#8217;m not all for is people taking an illogical premise, presenting it as fact, ignoring all evidence to the contrary, and then attempting to introduce new points when their argument is refuted. If you want to label anyone as a supporter of &#8220;grand design&#8221; in this argument, I&#8217;m afraid it&#8217;s you, my friend.</p>
<p>You write good stuff. This is a well-run site. Everyone gets things wrong from time to time. It&#8217;s OK! :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheCosmonaut</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-28003</link>
		<dc:creator>TheCosmonaut</dc:creator>
		<pubDate>Tue, 18 May 2010 01:14:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-28003</guid>
		<description>@Dan J
Well, let&#039;s consider your sources:
a) a professional Flash developer
Guess what - I am too. Over a decade worth of experience. So are a number of other commenters who disagree. And it appears that a some staff at Gizmodo agree with us as well. Critical thinking: because one Flash developer says it&#039;s so doesn&#039;t make it so. Particularly when evidence has been presented to the contrary.

&lt;em&gt;[I have to say I find it annoying and irritating that you think I should respond to this platform advocate/evangelist&#039;s troll as if it&#039;s a credible argument that demands serious attention. Also, you can cite yourself as a Flash developer with an informed opinion if you like, but once you claim anyone from Gizmodo as having something to contribute in terms of analytical skills, it again becomes difficult to take your position seriously. - Dan]&lt;/em&gt;

b) Steve Jobs
Where did Steve Jobs say that Flash couldn&#039;t be used on iPad because of the rollover (non-)issue? Critical thinking: This is the premise of your blog post. Steve Jobs doesn&#039;t support your assertion. You can&#039;t cite him as support.

&lt;em&gt;[The idea that navigation and gameplay is often dependent upon mouseovers is established in the article and you acknowledge it below. The idea in general that Flash isn&#039;t optimized as a platform for building touch-based interfaces but is subject to improvement as Adobe patches up its platform is a subject open to debate, but the fact that existing Flash content is dependent upon this is not controversial. Therefore Adobe&#039;s claim that today&#039;s existing Flash content is desperately important is completely undermined by the reality that none of it, from mouseover-dependent games to non-optimized video playback, really has all that much value at all. It&#039;s all obsolete and going away, so it doesn&#039;t matter if Adobe can fix some specific element. It&#039;s irrelevant. 

Jobs referenced Flash&#039;s lack of multitouch support in general terms, because the details are boring. The fact is, we can all work really hard here on out to entrench Flash as a future standard, or we can work on web standards and continue to build something that Adobe (or any other one company with interests in contrast to everyone else) doesn&#039;t own. There&#039;s a reason why people who are finically dependent upon Adobe are for Flash, and everyone who wants things to just work well doesn&#039;t care that much about it. ]&lt;/em&gt;

c) Me
I have to say, you don&#039;t seem like a trusted source. You&#039;re not a developer, you seem to have a clear bias in favor of Apple and are vehemently anti-Adobe (how many articles have you written as cricism of Adobe?), and have been unable to present any logical argument or citation for an exterior source to support your argument. By contrast, you&#039;ve been presented with a number of options which disprove your argument, including:

&lt;em&gt;[This is why I won&#039;t be responding to your future comments. You are being a complete dick. You throw out a bunch of unfounded claims, and then fellate a hysterical Adobe shill. I can&#039;t respect that. You&#039;re being a troll wasting my time without a real point. ]&lt;/em&gt;

* http://theflashblog.com/?p=2027  (you assert that this guy is hysterical and seem to imply therefore that his video was doctored or misleading in some fashion. Ok, so let&#039;s ignore this link)
* http://www.youtube.com/watch?v=ZIl1k7wX7Fk (this video shows how they addressed the lack of a literal mouse in mobile platforms. Seems like the rollover issue is a non-issue again. However, since this guy is an Adobe evangelist, you may assert this reference must be ignored as well. OK)
* As suggested, try running CloudBrowse on your iPhone, going to a Flash website, and attempting to interact with it. While the app is slow as hell, you can see that interaction works just fine.
Critical thinking: Should I take the word of someone who ignores multiple sources of evidence yet provides none of his own?

&lt;em&gt;[The evidence is that the most successful smartphone is doing fine without Flash, as are the most successful media players and tablets. In fact, the only people bleating about how great Flash is are people like you, who make their living from it. There is no evidence you&#039;re presenting here, just some attempts to ignore the overall problem and concentrate on pointless ways to find reasons why the industry should stand on its head to make excuses for and complex solutions to solve portions of the problem, so you can keep doing what you did and continue to profit from your relationship with Adobe. You&#039;re acting like you&#039;ve won an argument. You haven&#039;t, you&#039;ve just trolled out paragraphs of answers to the wrong questions. You think you are so very smart, but I disagree.]&lt;/em&gt;

By the way: I think the big bone of contention here is not whether gestural devices CAN support mouseovers (all the links above demonstrate that it IS possible). 

&lt;em&gt;[That was never the issue. Did you even read the article? ]&lt;/em&gt;

The bone of contention comes from two assumptions that Morgan makes:

» Assumption #1: &quot;The use of rollovers is so widespread in Flash applications, and so important to their functionality, that the loss of the rollover renders such a majority of Flash sites useless as to make Flash unusable.&quot; Unfortunately, the reality just isn&#039;t so. While Mouse_Over events are definitely used in Flash applications, most Flash websites usethem simply as decorative rollover effects. Most video players will pause and display controls on click, then stay visible for a period of time, allowing you to click and then control them. All other examples (such as tooltips, maps and diagrams, etc.) are basic &quot;web&quot; functionalities that apply to JavaScript as well as Flash, and it is therefore illogical to say that Flash is impossible to use while JavaScript is OK. I will agree, however, that a large number games will be broken without the mouse_over ability. Does that really mean that it is fundamentally &quot;illogical&quot; to use Flash? I would say no, but I have a feeling you will disagree :)
» Assumption #2: &quot;The only potential &#039;solutions&#039; to the mouseover problem are terrible ones.&quot; Most of the examples of Flash sites working fine on gestural devices that I provide above use Morgan&#039;s solution D) Having a visible mouse pointer. Morgan seems to feel that the visible mouse pointer is so awful as to render the whole gestural device pointless. I would argue that the examples provided above demonstrate that the solution is far from awful, and in fact provides an excellent user experience. Additionally, his assumption also rests on the premise that the only possible solutions are the ones he offers. With all due respect to Morgan, I believe there are other solutions out there. (Assuming it NEEDS to be solved in the first place... see my argument against Assumption #1).

Nobody likes admitting they&#039;re wrong. Just man up and do it on this point :D  Believe me, you have PLENTY of other, valid reasons to criticize Adobe!

&lt;em&gt;[Not only are Morgan&#039;s &quot;assumptions&quot; well presented, but you even agree with them enough to where your counter-arguments are irrelevant. And your huffing about non-important tangents fails to grasp that the  problem here is Flash, not Apple&#039;s lack of support for a player that doesn&#039;t yet exist, not my articles pointing out the fallacy of Adobe&#039;s arguments and its specious attacks that have no merit. The problem is that Flash is a shitty substitute for web standards within the browser, for a lot of interlocking reasons. You can&#039;t pick at one part of the overall argument and say, &quot;hey, there&#039;s a way we could make this touch stuff work if we do a bunch of clumsy backward stuff to support a terrible platform that is slow, full of bugs, riddled with security holes by design, and really doesn&#039;t need to exist.&quot; 

That&#039;s not an argument, certainly not something I have to &quot;concede&quot; to you, and I&#039;m left ashamed to have entered into a discussion where your ridiculous trolling has wasted my time. I might as well be arguing with the idea that life can not shift genetically and all the species on earth were handmade by a supernatural creator a few thousand years ago. 

Flash sucks, we knew that long before the iPhone showed up. Did you miss the memo on Java clients not being all that? It got passed around like ten years ago. Having another version of the same thing with not just greater dependance upon a single vendor, but having that vendor being the clusterfuck that is Adobe, is not an improvement that is going to make Flash/Flex a superior replacement for desktop Java, let alone JavaME. It&#039;s pretty clearly the same turd with a different owner  - Dan ]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>@Dan J<br />
Well, let&#8217;s consider your sources:<br />
a) a professional Flash developer<br />
Guess what &#8211; I am too. Over a decade worth of experience. So are a number of other commenters who disagree. And it appears that a some staff at Gizmodo agree with us as well. Critical thinking: because one Flash developer says it&#8217;s so doesn&#8217;t make it so. Particularly when evidence has been presented to the contrary.</p>
<p><em>[I have to say I find it annoying and irritating that you think I should respond to this platform advocate/evangelist's troll as if it's a credible argument that demands serious attention. Also, you can cite yourself as a Flash developer with an informed opinion if you like, but once you claim anyone from Gizmodo as having something to contribute in terms of analytical skills, it again becomes difficult to take your position seriously. - Dan]</em></p>
<p>b) Steve Jobs<br />
Where did Steve Jobs say that Flash couldn&#8217;t be used on iPad because of the rollover (non-)issue? Critical thinking: This is the premise of your blog post. Steve Jobs doesn&#8217;t support your assertion. You can&#8217;t cite him as support.</p>
<p><em>[The idea that navigation and gameplay is often dependent upon mouseovers is established in the article and you acknowledge it below. The idea in general that Flash isn't optimized as a platform for building touch-based interfaces but is subject to improvement as Adobe patches up its platform is a subject open to debate, but the fact that existing Flash content is dependent upon this is not controversial. Therefore Adobe's claim that today's existing Flash content is desperately important is completely undermined by the reality that none of it, from mouseover-dependent games to non-optimized video playback, really has all that much value at all. It's all obsolete and going away, so it doesn't matter if Adobe can fix some specific element. It's irrelevant. </p>
<p>Jobs referenced Flash's lack of multitouch support in general terms, because the details are boring. The fact is, we can all work really hard here on out to entrench Flash as a future standard, or we can work on web standards and continue to build something that Adobe (or any other one company with interests in contrast to everyone else) doesn't own. There's a reason why people who are finically dependent upon Adobe are for Flash, and everyone who wants things to just work well doesn't care that much about it. ]</em></p>
<p>c) Me<br />
I have to say, you don&#8217;t seem like a trusted source. You&#8217;re not a developer, you seem to have a clear bias in favor of Apple and are vehemently anti-Adobe (how many articles have you written as cricism of Adobe?), and have been unable to present any logical argument or citation for an exterior source to support your argument. By contrast, you&#8217;ve been presented with a number of options which disprove your argument, including:</p>
<p><em>[This is why I won't be responding to your future comments. You are being a complete dick. You throw out a bunch of unfounded claims, and then fellate a hysterical Adobe shill. I can't respect that. You're being a troll wasting my time without a real point. ]</em></p>
<p>* <a href="http://theflashblog.com/?p=2027" rel="nofollow">http://theflashblog.com/?p=2027</a>  (you assert that this guy is hysterical and seem to imply therefore that his video was doctored or misleading in some fashion. Ok, so let&#8217;s ignore this link)<br />
* <a href="http://www.youtube.com/watch?v=ZIl1k7wX7Fk" rel="nofollow">http://www.youtube.com/watch?v=ZIl1k7wX7Fk</a> (this video shows how they addressed the lack of a literal mouse in mobile platforms. Seems like the rollover issue is a non-issue again. However, since this guy is an Adobe evangelist, you may assert this reference must be ignored as well. OK)<br />
* As suggested, try running CloudBrowse on your iPhone, going to a Flash website, and attempting to interact with it. While the app is slow as hell, you can see that interaction works just fine.<br />
Critical thinking: Should I take the word of someone who ignores multiple sources of evidence yet provides none of his own?</p>
<p><em>[The evidence is that the most successful smartphone is doing fine without Flash, as are the most successful media players and tablets. In fact, the only people bleating about how great Flash is are people like you, who make their living from it. There is no evidence you're presenting here, just some attempts to ignore the overall problem and concentrate on pointless ways to find reasons why the industry should stand on its head to make excuses for and complex solutions to solve portions of the problem, so you can keep doing what you did and continue to profit from your relationship with Adobe. You're acting like you've won an argument. You haven't, you've just trolled out paragraphs of answers to the wrong questions. You think you are so very smart, but I disagree.]</em></p>
<p>By the way: I think the big bone of contention here is not whether gestural devices CAN support mouseovers (all the links above demonstrate that it IS possible). </p>
<p><em>[That was never the issue. Did you even read the article? ]</em></p>
<p>The bone of contention comes from two assumptions that Morgan makes:</p>
<p>» Assumption #1: &#8220;The use of rollovers is so widespread in Flash applications, and so important to their functionality, that the loss of the rollover renders such a majority of Flash sites useless as to make Flash unusable.&#8221; Unfortunately, the reality just isn&#8217;t so. While Mouse_Over events are definitely used in Flash applications, most Flash websites usethem simply as decorative rollover effects. Most video players will pause and display controls on click, then stay visible for a period of time, allowing you to click and then control them. All other examples (such as tooltips, maps and diagrams, etc.) are basic &#8220;web&#8221; functionalities that apply to JavaScript as well as Flash, and it is therefore illogical to say that Flash is impossible to use while JavaScript is OK. I will agree, however, that a large number games will be broken without the mouse_over ability. Does that really mean that it is fundamentally &#8220;illogical&#8221; to use Flash? I would say no, but I have a feeling you will disagree :)<br />
» Assumption #2: &#8220;The only potential &#8217;solutions&#8217; to the mouseover problem are terrible ones.&#8221; Most of the examples of Flash sites working fine on gestural devices that I provide above use Morgan&#8217;s solution D) Having a visible mouse pointer. Morgan seems to feel that the visible mouse pointer is so awful as to render the whole gestural device pointless. I would argue that the examples provided above demonstrate that the solution is far from awful, and in fact provides an excellent user experience. Additionally, his assumption also rests on the premise that the only possible solutions are the ones he offers. With all due respect to Morgan, I believe there are other solutions out there. (Assuming it NEEDS to be solved in the first place&#8230; see my argument against Assumption #1).</p>
<p>Nobody likes admitting they&#8217;re wrong. Just man up and do it on this point :D  Believe me, you have PLENTY of other, valid reasons to criticize Adobe!</p>
<p><em>[Not only are Morgan's "assumptions" well presented, but you even agree with them enough to where your counter-arguments are irrelevant. And your huffing about non-important tangents fails to grasp that the  problem here is Flash, not Apple's lack of support for a player that doesn't yet exist, not my articles pointing out the fallacy of Adobe's arguments and its specious attacks that have no merit. The problem is that Flash is a shitty substitute for web standards within the browser, for a lot of interlocking reasons. You can't pick at one part of the overall argument and say, "hey, there's a way we could make this touch stuff work if we do a bunch of clumsy backward stuff to support a terrible platform that is slow, full of bugs, riddled with security holes by design, and really doesn't need to exist." </p>
<p>That's not an argument, certainly not something I have to "concede" to you, and I'm left ashamed to have entered into a discussion where your ridiculous trolling has wasted my time. I might as well be arguing with the idea that life can not shift genetically and all the species on earth were handmade by a supernatural creator a few thousand years ago. </p>
<p>Flash sucks, we knew that long before the iPhone showed up. Did you miss the memo on Java clients not being all that? It got passed around like ten years ago. Having another version of the same thing with not just greater dependance upon a single vendor, but having that vendor being the clusterfuck that is Adobe, is not an improvement that is going to make Flash/Flex a superior replacement for desktop Java, let alone JavaME. It's pretty clearly the same turd with a different owner  - Dan ]</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fen</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-28001</link>
		<dc:creator>fen</dc:creator>
		<pubDate>Mon, 17 May 2010 23:29:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-28001</guid>
		<description>@DanJ:

&gt; the people disagreeing with you are a) a professional Flash developer 

Are you serious? I&#039;m a professional Flash developer, and almost surely have been so for longer than your source (since 2000). I&#039;m sure many other commenters are too. More importantly, the author of your article is a Flash developer who, when he was writing, had never seen Flash 10 on mobile devices. He was speculating; we are not.

&gt; b) Steve Jobs, who knows something about how Flash works

Steve Jobs, who recently attacked Adobe for being slow to move to Cocoa even though iTunes and Final Cut haven&#039;t moved yet. Messaging from Steve Jobs is marketing, not technical information.

&gt; c) Me.

i.e. a non-developer who, so far, has not been able to name a single website that suffers or will suffer the problems predicted in this article.</description>
		<content:encoded><![CDATA[<p>@DanJ:</p>
<p>&gt; the people disagreeing with you are a) a professional Flash developer </p>
<p>Are you serious? I&#8217;m a professional Flash developer, and almost surely have been so for longer than your source (since 2000). I&#8217;m sure many other commenters are too. More importantly, the author of your article is a Flash developer who, when he was writing, had never seen Flash 10 on mobile devices. He was speculating; we are not.</p>
<p>&gt; b) Steve Jobs, who knows something about how Flash works</p>
<p>Steve Jobs, who recently attacked Adobe for being slow to move to Cocoa even though iTunes and Final Cut haven&#8217;t moved yet. Messaging from Steve Jobs is marketing, not technical information.</p>
<p>&gt; c) Me.</p>
<p>i.e. a non-developer who, so far, has not been able to name a single website that suffers or will suffer the problems predicted in this article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: genegibson</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-27999</link>
		<dc:creator>genegibson</dc:creator>
		<pubDate>Mon, 17 May 2010 21:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-27999</guid>
		<description>The only potential “solutions” to the mouseover problem are terrible ones:
How about F: When a keyboard or Bluetooth mouse are attached, a Flash plugin works (from a Settings option).
--- As large as the onscreen keyboard is on the iPad, I&#039;m not going to learn how to &quot;hunt &amp; peck&quot; again.  I know how to type, and if I&#039;m going to do any serious wordprocessing, I&#039;m going to use a full sized keyboard.  And, it can&#039;t be something projected on a flat surface.  Knowing where certain starting keys are located (by feel, and you can&#039;t do that with a completely smooth surface) is necessary to touch typing.
 
But, what I would really like is voice command or voice to text that was relatively accurate.  Nuance has a product that is very close on the PC side.
---
Flickr could come up with a Flash alternative to it&#039;s Slideshow, but I&#039;m currently enamored by Prezi (which is Flash based).</description>
		<content:encoded><![CDATA[<p>The only potential “solutions” to the mouseover problem are terrible ones:<br />
How about F: When a keyboard or Bluetooth mouse are attached, a Flash plugin works (from a Settings option).<br />
&#8212; As large as the onscreen keyboard is on the iPad, I&#8217;m not going to learn how to &#8220;hunt &amp; peck&#8221; again.  I know how to type, and if I&#8217;m going to do any serious wordprocessing, I&#8217;m going to use a full sized keyboard.  And, it can&#8217;t be something projected on a flat surface.  Knowing where certain starting keys are located (by feel, and you can&#8217;t do that with a completely smooth surface) is necessary to touch typing.</p>
<p>But, what I would really like is voice command or voice to text that was relatively accurate.  Nuance has a product that is very close on the PC side.<br />
&#8212;<br />
Flickr could come up with a Flash alternative to it&#8217;s Slideshow, but I&#8217;m currently enamored by Prezi (which is Flash based).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheCosmonaut</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-27994</link>
		<dc:creator>TheCosmonaut</dc:creator>
		<pubDate>Sun, 16 May 2010 23:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-27994</guid>
		<description>fen has said it all. 

Dan, your whole premise of this article is, in your own words: 
&quot;Current Flash sites could never be made work well on any touchscreen device... because of the hover or mouseover problem.... They are coded to rely on the difference between hovering over something (mouseover) vs. actually clicking.&quot;

So if this is the point of your article, let&#039;s ignore &quot;slow mobile performance, battery drain or crashes&quot; as you say.

Now, go and watch the video at http://theflashblog.com/?p=2027. Check out the video links to examples on Android devices provided in the comments above. Recognize that whether a cursor is visible on the screen or not, the same programming elements are happening in the background.

You could also try installing CloudBrowse and going to a Flash site to see how it works (although CloudBrowse barely ever can connect).

Now realize that your original argument, namely that current Flash sites won&#039;t work because of the need for rollover &amp; click, is proven incorrect.

No big deal - there&#039;s plenty of other reasons to rant against Flash for Apple. Just admit that you got this one wrong :)

&lt;em&gt;[You can keep insisting that you&#039;re right and that you understand the issue, but just consider: the people disagreeing with you are a) a professional Flash developer who wrote the article I published b) Steve Jobs, who knows something about how Flash works and investigated putting it on the iPhone before rejecting it c) Me. In contrast, the person blowing smoke up your ass is the &quot;platform advocate&quot; of Flash, paid by Adobe to blog things that are often completely ridiculous, as his last post I mentioned, where Adobe actually had to edit his hysterics to avoid embarrassment. 

Consider the potential that you&#039;re failing to grasp the concept of critical thinking - Dan ]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>fen has said it all. </p>
<p>Dan, your whole premise of this article is, in your own words:<br />
&#8220;Current Flash sites could never be made work well on any touchscreen device&#8230; because of the hover or mouseover problem&#8230;. They are coded to rely on the difference between hovering over something (mouseover) vs. actually clicking.&#8221;</p>
<p>So if this is the point of your article, let&#8217;s ignore &#8220;slow mobile performance, battery drain or crashes&#8221; as you say.</p>
<p>Now, go and watch the video at <a href="http://theflashblog.com/?p=2027" rel="nofollow">http://theflashblog.com/?p=2027</a>. Check out the video links to examples on Android devices provided in the comments above. Recognize that whether a cursor is visible on the screen or not, the same programming elements are happening in the background.</p>
<p>You could also try installing CloudBrowse and going to a Flash site to see how it works (although CloudBrowse barely ever can connect).</p>
<p>Now realize that your original argument, namely that current Flash sites won&#8217;t work because of the need for rollover &amp; click, is proven incorrect.</p>
<p>No big deal &#8211; there&#8217;s plenty of other reasons to rant against Flash for Apple. Just admit that you got this one wrong :)</p>
<p><em>[You can keep insisting that you're right and that you understand the issue, but just consider: the people disagreeing with you are a) a professional Flash developer who wrote the article I published b) Steve Jobs, who knows something about how Flash works and investigated putting it on the iPhone before rejecting it c) Me. In contrast, the person blowing smoke up your ass is the "platform advocate" of Flash, paid by Adobe to blog things that are often completely ridiculous, as his last post I mentioned, where Adobe actually had to edit his hysterics to avoid embarrassment. </p>
<p>Consider the potential that you're failing to grasp the concept of critical thinking - Dan ]</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fen</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-27970</link>
		<dc:creator>fen</dc:creator>
		<pubDate>Sat, 15 May 2010 02:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-27970</guid>
		<description>@davesmall: 
As a developer, I would agree with every word you said if Apple was simply encouraging obj-C apps and discouraging platform layers. But they&#039;re not, they&#039;re legally requiring everyone to use one tool over another. What if future revisions to obj-C suck, and developers would be more productive writing their logic in Lua? Tough, they&#039;re legally required to use obj-C even if it&#039;s not the best choice. What if Unity3D does some mad innovation, and allows developers to build apps that run faster than they would if made in obj-C? Tough, devs will be legally required to use the worse technology. It&#039;s the very definition of stifling innovation.

But you&#039;re right that the change is in Apple&#039;s best interest. It&#039;s just not in user&#039;s best interest, and it&#039;s very very very not in developer&#039;s best interest. I mean, there&#039;s no getting around it - if obj-C is best, developers and users can choose it. The problem is that if obj-C isn&#039;t best, they&#039;re still legally prevented from choosing anything else.</description>
		<content:encoded><![CDATA[<p>@davesmall:<br />
As a developer, I would agree with every word you said if Apple was simply encouraging obj-C apps and discouraging platform layers. But they&#8217;re not, they&#8217;re legally requiring everyone to use one tool over another. What if future revisions to obj-C suck, and developers would be more productive writing their logic in Lua? Tough, they&#8217;re legally required to use obj-C even if it&#8217;s not the best choice. What if Unity3D does some mad innovation, and allows developers to build apps that run faster than they would if made in obj-C? Tough, devs will be legally required to use the worse technology. It&#8217;s the very definition of stifling innovation.</p>
<p>But you&#8217;re right that the change is in Apple&#8217;s best interest. It&#8217;s just not in user&#8217;s best interest, and it&#8217;s very very very not in developer&#8217;s best interest. I mean, there&#8217;s no getting around it &#8211; if obj-C is best, developers and users can choose it. The problem is that if obj-C isn&#8217;t best, they&#8217;re still legally prevented from choosing anything else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davesmall</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-27950</link>
		<dc:creator>davesmall</dc:creator>
		<pubDate>Fri, 14 May 2010 18:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-27950</guid>
		<description>Adobe&#039;s customer is the developer who wants his work to run the same on multiple platforms. That&#039;s what Adobe is selling - cross platform development tools. According to Adobe, it&#039;s a good thing for customers if applications are the same on various platforms.

Well now, I&#039;m a customer and I prefer Apple&#039;s products. I could care less if they run on Windows or Linux or whatever. Furthermore, I dislike applications like TweetDeck that have an unfamiliar user interface.  I think that was developed on one of Adobe&#039;s platforms.

Apple must believe that companies like Microsoft, Nokia, Motorola, HTC, Palm, HP, Google, Dell, and Research in Motion are all working hard to create iPhone and iPad knock-offs. I think that&#039;s obviously true. Before the iPhone there was nothing like it. Now these companies are all coming out with iPhone knock-offs. So why should Apple assist them in their copying efforts by making it easier for them to run software created for Apple&#039;s platforms? 

Seems to me that Steve Jobs arguments are pretty much correct. It is in Apple&#039;s best interests, Apple customer&#039;s best interest, and loyal Apple developer&#039;s (those who write Apps using the Apple SDK and Objective C) to discourage cross-platform developer tools. So what if Flash developed products would run OK on the iPhone? That&#039;s not the point.</description>
		<content:encoded><![CDATA[<p>Adobe&#8217;s customer is the developer who wants his work to run the same on multiple platforms. That&#8217;s what Adobe is selling &#8211; cross platform development tools. According to Adobe, it&#8217;s a good thing for customers if applications are the same on various platforms.</p>
<p>Well now, I&#8217;m a customer and I prefer Apple&#8217;s products. I could care less if they run on Windows or Linux or whatever. Furthermore, I dislike applications like TweetDeck that have an unfamiliar user interface.  I think that was developed on one of Adobe&#8217;s platforms.</p>
<p>Apple must believe that companies like Microsoft, Nokia, Motorola, HTC, Palm, HP, Google, Dell, and Research in Motion are all working hard to create iPhone and iPad knock-offs. I think that&#8217;s obviously true. Before the iPhone there was nothing like it. Now these companies are all coming out with iPhone knock-offs. So why should Apple assist them in their copying efforts by making it easier for them to run software created for Apple&#8217;s platforms? </p>
<p>Seems to me that Steve Jobs arguments are pretty much correct. It is in Apple&#8217;s best interests, Apple customer&#8217;s best interest, and loyal Apple developer&#8217;s (those who write Apps using the Apple SDK and Objective C) to discourage cross-platform developer tools. So what if Flash developed products would run OK on the iPhone? That&#8217;s not the point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chipotle</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-27948</link>
		<dc:creator>Chipotle</dc:creator>
		<pubDate>Fri, 14 May 2010 18:34:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-27948</guid>
		<description>@dazweeja: I did see the videos and I&#039;ve read some of the documentation from Adobe on this. My comment wasn&#039;t about Flash, per se, as much as about the futility of this argument. :) Mr. Dilger&#039;s mind is pretty clearly made up and I don&#039;t think he&#039;s interested in whether Adobe has actually solved these problems in the upcoming release. But it really doesn&#039;t matter whether he remains unconvinced or not, since on a practical level it&#039;s about what Apple wants on their platform and so far Flash is clearly not something they want. Demonstrating that Flash 10.1 will figure out the right events to map from touch to mouse and so there won&#039;t need to be as many changes as one might think is only going to go so far. I&#039;m not entirely convinced by Mike Chambers&#039; demo in that it seems to be sending an awful lot of events at once (it&#039;s the rollover-click-down-up event!), but even if that works great it doesn&#039;t take advantage of the touch interface very well: using multitouch will require new code, and some serious UI rethinking. Remember, Apple are the bastards who left off arrow keys from the original Mac expressly to make it difficult to port apps that relied on them because they wanted to push the mouse. Replace &quot;mouse&quot; with &quot;multitouch&quot; here.

Again, in practice it&#039;s going to be a market decision. If Apple is wrong to cut Flash out and to make it difficult to use anything but their own approved languages, they&#039;ll find out the hard way. The problem is that right now the market really isn&#039;t punishing them for the choices they&#039;ve made. (The recent reports that there are now more Android devices being sold than iPhones is the first chink in the armor, but that&#039;s a rebuke to their exclusivity with AT&amp;T, I suspect.)</description>
		<content:encoded><![CDATA[<p>@dazweeja: I did see the videos and I&#8217;ve read some of the documentation from Adobe on this. My comment wasn&#8217;t about Flash, per se, as much as about the futility of this argument. :) Mr. Dilger&#8217;s mind is pretty clearly made up and I don&#8217;t think he&#8217;s interested in whether Adobe has actually solved these problems in the upcoming release. But it really doesn&#8217;t matter whether he remains unconvinced or not, since on a practical level it&#8217;s about what Apple wants on their platform and so far Flash is clearly not something they want. Demonstrating that Flash 10.1 will figure out the right events to map from touch to mouse and so there won&#8217;t need to be as many changes as one might think is only going to go so far. I&#8217;m not entirely convinced by Mike Chambers&#8217; demo in that it seems to be sending an awful lot of events at once (it&#8217;s the rollover-click-down-up event!), but even if that works great it doesn&#8217;t take advantage of the touch interface very well: using multitouch will require new code, and some serious UI rethinking. Remember, Apple are the bastards who left off arrow keys from the original Mac expressly to make it difficult to port apps that relied on them because they wanted to push the mouse. Replace &#8220;mouse&#8221; with &#8220;multitouch&#8221; here.</p>
<p>Again, in practice it&#8217;s going to be a market decision. If Apple is wrong to cut Flash out and to make it difficult to use anything but their own approved languages, they&#8217;ll find out the hard way. The problem is that right now the market really isn&#8217;t punishing them for the choices they&#8217;ve made. (The recent reports that there are now more Android devices being sold than iPhones is the first chink in the armor, but that&#8217;s a rebuke to their exclusivity with AT&amp;T, I suspect.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fen</title>
		<link>http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/comment-page-5/#comment-27943</link>
		<dc:creator>fen</dc:creator>
		<pubDate>Fri, 14 May 2010 16:34:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=4191#comment-27943</guid>
		<description>Indeed, the salient point is that Flash only has a certain number of events, and they all get dispatched from both touch and mouse interactions. The only way you can really go about building content to break is by putting important interactions inside hover events, and specifically disabling them every time a mouse_down takes place and re-enabling them when the mouse is released. Which you can do if you like, of course, but it&#039;s absurd to go around saying that &quot;most&quot; or &quot;all&quot; content uses such an odd style of interaction.

With that said though, dazweeja, I think the trouble with the video people keep linking is that Dan won&#039;t have any take on it at all. In this post he relayed arguments that were supposed to support a conclusion he agrees with, but his agreement was never actually based on those arguments. He believed it before the arguments were made, because he&#039;s the kind of person who says things like &quot;flashtard&quot;, so it&#039;s natural that he should continue believing in it after the arguments turn out not to reflect reality.

Unfortunately I think this is what tends to happen when non-developers speculate on technology... People who program must unavoidably keep accurate opinions on the tech they use, or they won&#039;t be able to make anything, but people who merely comment are under no such obligation.</description>
		<content:encoded><![CDATA[<p>Indeed, the salient point is that Flash only has a certain number of events, and they all get dispatched from both touch and mouse interactions. The only way you can really go about building content to break is by putting important interactions inside hover events, and specifically disabling them every time a mouse_down takes place and re-enabling them when the mouse is released. Which you can do if you like, of course, but it&#8217;s absurd to go around saying that &#8220;most&#8221; or &#8220;all&#8221; content uses such an odd style of interaction.</p>
<p>With that said though, dazweeja, I think the trouble with the video people keep linking is that Dan won&#8217;t have any take on it at all. In this post he relayed arguments that were supposed to support a conclusion he agrees with, but his agreement was never actually based on those arguments. He believed it before the arguments were made, because he&#8217;s the kind of person who says things like &#8220;flashtard&#8221;, so it&#8217;s natural that he should continue believing in it after the arguments turn out not to reflect reality.</p>
<p>Unfortunately I think this is what tends to happen when non-developers speculate on technology&#8230; People who program must unavoidably keep accurate opinions on the tech they use, or they won&#8217;t be able to make anything, but people who merely comment are under no such obligation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
