<?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: A Tangible (negative) Impact of the Sun/MySQL Acquistion</title>
	<atom:link href="http://www.barkingseal.com/2009/05/tangible-negitive-impact-of-the-sunmysql-acquistion/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.barkingseal.com/2009/05/tangible-negitive-impact-of-the-sunmysql-acquistion/</link>
	<description>Applied Trust off-leash: IT infrastructure, security, and performance</description>
	<lastBuildDate>Thu, 29 Jul 2010 20:30:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: David Lovering</title>
		<link>http://www.barkingseal.com/2009/05/tangible-negitive-impact-of-the-sunmysql-acquistion/comment-page-1/#comment-65</link>
		<dc:creator>David Lovering</dc:creator>
		<pubDate>Sat, 13 Jun 2009 19:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.barkingseal.com/?p=834#comment-65</guid>
		<description>A lot of government sites have taken JPL&#039;s initiative to transition away from Oracle in favor of various turnkey-hardened versions of MySQL over the last &quot;n&quot; years, benefiting both their performance and budget constraints.  While no one will argue that MySQL has all the bells-and-whistles that Oracle does, the bulk of the added-value is illusory: many of the calls are either little-used or can be constructed easily out of modified SELECT, JOIN or other comparable components of MySQL.

This overhead has historically added other benefits as well: installing Oracle 10g in a &quot;Best-Practices&quot; configuration requires a week and and stack of manuals; installing a hardened version of MySQL - maybe an hour.  [All exaggerations can be attributed to the lack of lucidity in the Oracle manuals].

Sun&#039;s acquiring MySQL was bad enough - a partnership would have fulfilled the same business objectives without compromising the expectations of the GPL crowd, but Oracle?  That&#039;s like selling the American Cancer Society into bondage to Phillip Morris; and the penalties are to be felt on both sides of the fence.

As long as MySQL was a free-agent in the marketplace Oracle was kept under the gun to accelerate the performance of its own products, streamline the packages to be slightly less memory hoggish, and generally provide a tighter end product.  Now, with their major performance competitor tidily wedged in their hip pocket, Oracle can return to its former state of dormancy and relax the QA frenzy that resulted from a little honest competition.

This is of course a gross over-simplification: MySQL retains at least a vestige of an existence outside Sun/Oracle, and I&#039;m sure stock options have been generously exchanged under the table.  Never-the-less, the public&#039;s expectations of a real and substantial counter to Oracle&#039;s excessive and Draconian licensing strictures are at lest temporarily dashed.

Darth Vader finally won thru.</description>
		<content:encoded><![CDATA[<p>A lot of government sites have taken JPL&#8217;s initiative to transition away from Oracle in favor of various turnkey-hardened versions of MySQL over the last &#8220;n&#8221; years, benefiting both their performance and budget constraints.  While no one will argue that MySQL has all the bells-and-whistles that Oracle does, the bulk of the added-value is illusory: many of the calls are either little-used or can be constructed easily out of modified SELECT, JOIN or other comparable components of MySQL.</p>
<p>This overhead has historically added other benefits as well: installing Oracle 10g in a &#8220;Best-Practices&#8221; configuration requires a week and and stack of manuals; installing a hardened version of MySQL &#8211; maybe an hour.  [All exaggerations can be attributed to the lack of lucidity in the Oracle manuals].</p>
<p>Sun&#8217;s acquiring MySQL was bad enough &#8211; a partnership would have fulfilled the same business objectives without compromising the expectations of the GPL crowd, but Oracle?  That&#8217;s like selling the American Cancer Society into bondage to Phillip Morris; and the penalties are to be felt on both sides of the fence.</p>
<p>As long as MySQL was a free-agent in the marketplace Oracle was kept under the gun to accelerate the performance of its own products, streamline the packages to be slightly less memory hoggish, and generally provide a tighter end product.  Now, with their major performance competitor tidily wedged in their hip pocket, Oracle can return to its former state of dormancy and relax the QA frenzy that resulted from a little honest competition.</p>
<p>This is of course a gross over-simplification: MySQL retains at least a vestige of an existence outside Sun/Oracle, and I&#8217;m sure stock options have been generously exchanged under the table.  Never-the-less, the public&#8217;s expectations of a real and substantial counter to Oracle&#8217;s excessive and Draconian licensing strictures are at lest temporarily dashed.</p>
<p>Darth Vader finally won thru.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
