<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Some Random Dude &#187; javascript</title>
	<atom:link href="http://www.somerandomdude.com/tag/javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.somerandomdude.com</link>
	<description>Some Random Dude is a blog by P.J. Onori that covers design &#38; technology in the broadest sense possible.</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:37:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Past Processing work by Marius Watz ported to Javascript through&#8230;</title>
		<link>http://www.somerandomdude.com/2010/10/27/past-processing-work-by-marius-watz-ported-to-javascript-through/</link>
		<comments>http://www.somerandomdude.com/2010/10/27/past-processing-work-by-marius-watz-ported-to-javascript-through/#comments</comments>
		<pubDate>Wed, 27 Oct 2010 15:50:08 +0000</pubDate>
		<dc:creator>P.J. Onori</dc:creator>
				<category><![CDATA[Found Elsewhere]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[Processing]]></category>

		<guid isPermaLink="false">http://somerandomdude.com/stream/tumblr/past-processing-work-by-marius-watz-ported-to-javascript-through/</guid>
		<description><![CDATA[Past Processing work by Marius Watz ported to Javascript through Processing.js.]]></description>
			<content:encoded><![CDATA[<p><img src="/wp-content/uploads/cc183_tumblr_laygz5zwDy1qznk6ho1_500.png" />
<p>Past Processing work by <a href="http://workshop.evolutionzone.com/2010/10/27/work-abstract01js/">Marius Watz</a> ported to Javascript through <a href="http://processingjs.org/">Processing.js</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.somerandomdude.com/2010/10/27/past-processing-work-by-marius-watz-ported-to-javascript-through/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Anti-Flash Standardistas &#8211; You&#8217;re Cutting Off Your Nose to Spite Your Face</title>
		<link>http://www.somerandomdude.com/2006/12/04/anti-flash-standardistas/</link>
		<comments>http://www.somerandomdude.com/2006/12/04/anti-flash-standardistas/#comments</comments>
		<pubDate>Mon, 04 Dec 2006 11:04:26 +0000</pubDate>
		<dc:creator>P.J. Onori</dc:creator>
				<category><![CDATA[Design Technology]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[javascript]]></category>

		<guid isPermaLink="false">http://www.somerandomdude.net/blog/flash/anti-flash-standardistas/</guid>
		<description><![CDATA[The more I read attacks on Flash, the more I end up shaking my head in confusion. Honestly, I am a little surprised this is still being debated. People, we need to get over this. Before I elaborate further, I want to make clear my support for web standards, usability and accessibility. Additionally, I understand [...]]]></description>
			<content:encoded><![CDATA[<p><span class="callout">The more I read attacks on Flash, the more I end up shaking my head in confusion. Honestly, I am a little surprised this is still being debated. People, we need to get over this. Before I elaborate further, I want to make clear my support for web standards, usability and accessibility. Additionally, I understand the concern with Flash &#8211; it is not as easy to make accessible compared to HTML/CSS, it has, and continues, to be used for some really stupid things, etc., etc., etc. We have all been down that road, we have heard the arguments. That being said, standardistas: you are fighting a losing battle, and on top of it, a battle not worth fighting. Flash is about as standards-friendly as any media plug-in there is. For each bad use of Flash, there are hundreds being used well. Lastly, and more importantly, it is changing what we can do on a browser and how our generation accesses media. Please, for everyone&#8217;s sake, stop griping about Flash and start educating people on how it can be used more effectively with standards and accessibility in mind.</span><br />
<span id="more-238"></span><br />
I have been developing with Flash for the last four years. Nonetheless, my philosophy is that if something can be done outside of Flash, it should. In fact, I have <a href="/blog/flash/thinking-outside-flash-embed-box/">written</a> on ways to minimize the amount of Flash used in certain areas. However, due to the fact that HTML was never designed to handle rich media (video, audio, vector-base imagery, motion, etc.), the overwhelming majority of rich media delivery cannot be done on the HTML layer. This becomes abundantly obvious due to the plethora of length tutorials on how to round corners or put a drop-shadow on a rectangle. In fact, I would argue that Flash is the ONLY way to deliver rich media &#8211; all other technologies (Windows Media Player, Quicktime, Real, etc.) are not only <a href="http://www.adobe.com/products/player_census/flashplayer/tech_breakdown.html">less pervasive on the internet</a>, they are infinitely less flexible. The whole UGC (user-generated content) revolution would not have happened without Flash technologies pushing the content to viewers. Flash made this happen. Not standards (have you taken a look at YouTube&#8217;s HTML?), not AJAX, but Flash. I am not trying to diminish the necessity for web standards or AJAX, but many of the standards-manics seem to have their heads in the sand as to what Flash-enabled sites are achieving. In my opinion, the people that are still clenching onto the archaic notion that Flash is not necessary are diluting the discussion on web standards. Rather than deny its merits and accomplishments, why not work to push it further into the circle of accessibility and standards? No one wants technology and progress to be stifled in the name of standardization.</p>
<p>With Flash you have a plugin in which <a href="http://www.adobe.com/products/player_census/flashplayer/version_penetration.html">nearly 100%</a> of users have at least some version of the player on their system. The makers have been working to make the technology much more accessible (can you say the same for Windows Media Player or Quicktime?). In addition, Flash allows things to be done that HTML/CSS/Javascript will NEVER be able to do barring some paradigm shift in the technologies. We hear quite a bit about how Flash is not as accessible as HTML/CSS/Javascript  &#8211; ironically, the same people that are trying to replace Flash with extremely complex AJAX applications are nearly 200Kb of Javascript for the libraries alone (scriptaculous and prototype are roughly 190Kb combined). I developed the Current TV video player which stands at roughly 54Kb. A more basic and generic version of the same application could easily be under 20Kb. I am the first person to suggest keeping as much in HTML as possible. I am also one of the largest proponents of well-used AJAX. That being said, it is simply obtuse to attempt certain things outside of Flash &#8211; here are a few examples:</p>
<ul>
<li>Advanced visualizations</li>
<li>Advanced motion treatment</li>
<li>Physics engines</li>
<li>Projects where visual typographic control is paramount</li>
<li>Video or audio playback</li>
<li>Video or audio recording through a webcam</li>
<li>Rich-media browser based games</li>
<li>All of the above occurring simultaneously</li>
</ul>
<p>Ironcially, when you add up all the traffic from fringe browsers which are incompatible with the highly used Javascript libraries, it comes very close to the amount of users without the Flash player&#8230;</p>
<p>I would highly suggest giving Flash a serious second look. There are many new features that offer more accessible-centric options for development and design. Flash 8 and above offers new features for talking with Javascript &#8211; giving the potential for all interactive elements to be in standard HTML with Flash simply being the display. The express-install feature allows viewers to upgrade their version of Flash from the SWF on your own site &#8211; making upgrading much easier and much less cumbersome of a task. You are most likely going to find a lot of features you did not know existed which open the door to accessibility on the web.</p>
<p>I have no doubt the anti-flash standards folks mean well. That being said, should we not be devoting our energy towards making this technology more seamless throughout the browsing experience rather than pretend that it will just go away? And honestly, if it did somehow go away, would the web be a better place because of it?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.somerandomdude.com/2006/12/04/anti-flash-standardistas/feed/</wfw:commentRss>
		<slash:comments>24</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc (Feed is rejected)
Page Caching using apc
Database Caching 1/13 queries in 0.011 seconds using apc
Object Caching 295/315 objects using apc

Served from: www.somerandomdude.com @ 2012-02-09 15:56:42 -->
