<!DOCTYPE html>
<!-- ========================================== kroc camen of camen design ============================================= -->
<title>blog · A Tongue-in-Cheek Translation of Google’s Announcement to Bundle Flash With Chrome</title>
<link rel="stylesheet" type="text/css" href="/design/design.css" />
<meta name="viewport" content="width=device-width, maximum-scale=1.0, user-scalable=no" />
<link rel="alternate" type="application/rss+xml" href="/blog/rss" title="Just blog" />
<link rel="canonical" href="/blog/chrome_flash" />
<!-- =================================================================================================================== -->
<header>
	<h1><a href="/" rel="index">
		Camen Design
	</a></h1>
	<nav><ul>
		<li><a href="/">all</a></li>
		<li><a href="/projects">projects</a></li>
		<li><a href="http://forum.camendesign.com">forum</a></li>
	</ul><ul>
		<li><a href="/quote/">quote</a></li>
		<li><a href="/writing/">writing</a></li>
		<li><a href="/blog/" rel="tag">blog</a></li>
		<li><a href="/photo/">photo</a></li>
		<li><a href="/code/">code</a></li>
		<li><a href="/art/">art</a></li>
		<li><a href="/link/">link</a></li>
		<li><a href="/poem/">poem</a></li>
		<li><a href="/audio/">audio</a></li>
	</ul><ul>
		<li><a href="/web-dev/">web-dev</a></li>
		<li><a href="/annoyances/">annoyances</a></li>
		<li><a href="/eve/">eve</a></li>
		<li><a href="/code-is-art/">code-is-art</a></li>
		<li><a href="/inspiration/">inspiration</a></li>
		<li><a href="/windows/">windows</a></li>
		<li><a href="/gift/">gift</a></li>
		<li><a href="/gaming/">gaming</a></li>
		<li><a href="/mac/">mac</a></li>
		<li><a href="/osnews/">osnews</a></li>
		<li><a href="/c64/">c64</a></li>
		<li><a href="/linux/">linux</a></li>
	</ul>
	<a rel="previous" href="/blog/insecurities">
		older article →
	</a><a rel="next" href="/blog/flash_free_week">
		← newer article
	</a></nav>
</header>
<!-- =================================================================================================================== -->
<article><header>
	<!-- date published or updated -->
	<time pubdate datetime="2010-03-31T15:23:00+01:00">
		<sup>3:23<abbr>pm</abbr> • 2010</sup>
		<abbr title="March">Mar</abbr> 31
	</time>
	<!-- categories -->
	<ul>
		<li><a href="/blog/chrome_flash" rel="bookmark tag">blog</a></li>
		<li><a href="/web-dev/chrome_flash">web-dev</a></li>
	</ul>
	<!-- licence -->
	<small>
		<abbr title="copyright">©</abbr>
		copyright
	</small>
</header>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<section>
<h1>A Tongue-in-Cheek Translation of Google’s Announcement to Bundle Flash With Chrome</h1>
<p>
	<strong>Nobody dresses up the language</strong> in an announcement
	<a href="http://blog.chromium.org/2010/03/bringing-improved-support-for-adobe.html" rel="external">this
	much</a>,<br />
	unless they’re speaking through gritted teeth.
</p>
<blockquote>
	<p>
		Adobe Flash Player is the most widely used web browser plug-in. It enables a wide range of applications and
		content on the Internet, from games, to video, to enterprise apps.
	</p>
</blockquote>
<p>
	Flash is not our problem, but we have been forced to take action.
</p>
<blockquote>
	<p>
		The traditional browser plug-in model has enabled tremendous innovation on the web, but it also presents
		challenges for both plug-ins and browsers. The browser plug-in interface is loosely specified, limited in
		capability and varies across browsers and operating systems. This can lead to incompatibilities, reduction
		in performance and some security headaches.
	</p>
</blockquote>
<p>
	Web standards and browsers almost died completely.
</p>
<blockquote>
	<p>
		That’s why we are working with Adobe, Mozilla and the broader community to help define the next
		generation browser plug-in API. This new API aims to address the shortcomings of the current browser
		plug-in model. There is much to do and we’re eager to get started.
	</p>
</blockquote>
<p>
	We told Adobe to get their act together. We are not afraid of Mozilla, but begrudge having to constantly point them
	in the right direction.
</p>
<blockquote>
	<p>
		As a first step, we’ve begun collaborating with Adobe to improve the Flash Player experience in Google
		Chrome. Today, we’re making available an initial integration of Flash Player with Chrome in the developer
		channel. We plan to bring this functionality to all Chrome users as quickly as we can.
	</p>
</blockquote>
<p>
	We told Adobe to fix their crap or we wouldn’t ship Flash with Chrome OS.
</p>
<blockquote>
	<p>
		We believe this initiative will help our users in the following ways:
	</p>
	<ul>
		<li>When users download Chrome, they will also receive the latest version of Adobe Flash Player. There
		will be no need to install Flash Player separately.</li>
	</ul>
</blockquote>
<p>
	Adobe’s website is a joke, and forcing unwanted downloaders, Firefox extensions and copies of McAfee Security Scan
	on users is unacceptable.
</p>
<blockquote>
	<ul>
		<li>Users will automatically receive updates related to Flash Player using Google Chrome’s auto-update
		mechanism. This eliminates the need to manually download separate updates and reduces the security
		risk of using outdated versions.</li>
	</ul>
</blockquote>
<p>
	Adobe’s security is as tight as a clown’s pocket.
</p>
<blockquote>
	<ul>
		<li>With Adobe’s help, we plan to further protect users by extending Chrome’s “sandbox” to web
		pages with Flash content.</li>
	</ul>
</blockquote>
<p>
	We aim to protect users from Adobe, because they can’t be trusted to get it right.
</p>
<blockquote>
	<p>
		Improving the traditional browser plug-in model will make it possible for plug-ins to be just as fast,
		stable, and secure as the browser’s HTML and JavaScript engines. Over time this will enable HTML, Flash,
		and other plug-ins to be used together more seamlessly in rendering and scripting.
	</p>
</blockquote>
<p>
	There will always be brain-dead developers in the world who insist on using dead-end technologies like Flash and
	Silverlight.
</p>
<blockquote>
	<p>
		These improvements will encourage innovation in both the HTML and plug-in landscapes, improving the web
		experience for users and developers alike.
	</p>
</blockquote>
<p>
	Adobe is going to get double-boned by HTML5 / The iPad.
</p>
</section>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
</article>
<footer>
	<nav><a href="http://forum.camendesign.com">‹ Discuss this in the Forum ›</a></nav>
		
	<a href="mailto:kroc@camendesign.com">kroc@camendesign.com</a>
	<nav>view-source:
		<a href="/blog/chrome_flash.rem">Rem</a> •
		<a href="/blog/chrome_flash.html">HTML</a> •
		<a href="/design/">CSS</a> •
		<a href="/.system/">PHP</a> •
		<a href="/.htaccess">.htaccess</a>
	</nav>
	<form method="get" action="https://duckduckgo.com">
		<input type="hidden" name="sites" value="camendesign.com" />
		<input type="search" name="q" placeholder="search…" />
		<input type="submit" value="Go" />
	</form>
</footer>
<!-- =================================================================================================== code is art === -->