<?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>Developers, Developers, Developers! &#187; success story</title>
	<atom:link href="http://maksim.sorokin.dk/it/tag/success-story/feed/" rel="self" type="application/rss+xml" />
	<link>http://maksim.sorokin.dk/it</link>
	<description>Maksim Sorokin IT Blog</description>
	<lastBuildDate>Sun, 05 Feb 2012 19:37:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
		<item>
		<title>Why IzPack?</title>
		<link>http://maksim.sorokin.dk/it/2010/06/09/why-izpack/</link>
		<comments>http://maksim.sorokin.dk/it/2010/06/09/why-izpack/#comments</comments>
		<pubDate>Wed, 09 Jun 2010 15:55:09 +0000</pubDate>
		<dc:creator>Maksim Sorokin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[installation]]></category>
		<category><![CDATA[IzPack]]></category>
		<category><![CDATA[success story]]></category>

		<guid isPermaLink="false">http://maksim.sorokin.dk/it/?p=229</guid>
		<description><![CDATA[At some point instead of shipping a product to a customer and doing some postconfigurations afterwards one decides to create an installer, which would handle all the process. Of course, having an installer is not an easy task -- installer needs to be changed along with your product. Testing the installer and supporting uninstallation are [...]]]></description>
			<content:encoded><![CDATA[<p>At some point instead of shipping a product to a customer and doing some postconfigurations afterwards one decides to create an installer, which would handle all the process. Of course, having an installer is not an easy task -- installer needs to be changed along with your product. Testing the installer and supporting uninstallation are not trivial tasks as well..<span id="more-229"></span></p>
<p>But! Think of the advantages which you gain. Software is installed with double-click. No need to support long documentation manuals on configuration since a lot of stuff will be done automatically.</p>
<p>We decided to use <a href="http://izpack.org/">IzPack installer</a> for one of our products. Although there are plenty of other different installers, we chose this one since it is pretty simple, robust and free! I would like to start a small series of posts about IzPack covering integration with <a href="http://maven.apache.org/">Maven</a>, plugin development, debugging with <a href="http://www.eclipse.org/">Eclipse</a>, making modularized installers (which can be included in each other) and so on.</p>
]]></content:encoded>
			<wfw:commentRss>http://maksim.sorokin.dk/it/2010/06/09/why-izpack/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Memory Leak in Haskell During File Read 3</title>
		<link>http://maksim.sorokin.dk/it/2010/05/23/memory-leak-in-haskell-during-file-read-3/</link>
		<comments>http://maksim.sorokin.dk/it/2010/05/23/memory-leak-in-haskell-during-file-read-3/#comments</comments>
		<pubDate>Sun, 23 May 2010 05:13:47 +0000</pubDate>
		<dc:creator>Maksim Sorokin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[functional programming]]></category>
		<category><![CDATA[Haskell]]></category>
		<category><![CDATA[memory leak]]></category>
		<category><![CDATA[success story]]></category>

		<guid isPermaLink="false">http://maksim.sorokin.dk/it/?p=213</guid>
		<description><![CDATA[Problem described in previous two posts (1 2) has finally been fully understood and solved. Guys from #haskell channel on freenode IRC servers pointed me to the problem. The thing is that in the memory leak example I took length of read file and appended it to accumulator, which was sent further in the tail [...]]]></description>
			<content:encoded><![CDATA[<p>Problem described in previous two posts (<a href="http://maksim.sorokin.dk/it/2010/05/18/memory-leak-in-haskell-during-file-read/">1</a> <a href="http://maksim.sorokin.dk/it/2010/05/19/memory-leak-in-haskell-during-file-read-2/">2</a>) has finally been fully understood and solved. Guys from #haskell channel on <a href="http://freenode.net/irc_servers.shtml">freenode IRC servers</a> pointed me to the problem.</p>
<p>The thing is that <span id="more-213"></span>in the memory leak <a href="http://maksim.sorokin.dk/it/2010/05/18/memory-leak-in-haskell-during-file-read/">example</a> I took length of read file and appended it to accumulator, which was sent further in the tail call. And this accumulator was evaluated lazily! After adding <a href="http://users.aber.ac.uk/afc/stricthaskell.html#seq">strict sequencing operator</a>, the memory leak gone.</p>
<p>So instead of tail call:</p>
<pre class="brush: plain; title: ;">test fns $ acc + (B.length contents)</pre>
<p>I should have used:</p>
<pre class="brush: plain; title: ;">test fns $! acc + (B.length contents)</pre>
]]></content:encoded>
			<wfw:commentRss>http://maksim.sorokin.dk/it/2010/05/23/memory-leak-in-haskell-during-file-read-3/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>How We Upgraded Our VMware</title>
		<link>http://maksim.sorokin.dk/it/2010/02/26/how-we-upgraded-our-vmware/</link>
		<comments>http://maksim.sorokin.dk/it/2010/02/26/how-we-upgraded-our-vmware/#comments</comments>
		<pubDate>Fri, 26 Feb 2010 22:32:00 +0000</pubDate>
		<dc:creator>Maksim Sorokin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[success story]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://maksim.sorokin.dk/it/?p=80</guid>
		<description><![CDATA[We have just finished upgrading our VMware -- vCenter Server, ESX on our hosts and virtual machines to the forth version. We expected to spend all weekend on this, but it turned out we managed to upgrade in just about 5-6 hours! And that is without any previous serious experience with VMware! Well, yes, we [...]]]></description>
			<content:encoded><![CDATA[<p>We have just finished upgrading our VMware -- vCenter Server, ESX on our hosts and virtual machines to the forth version. We expected to spend all weekend on this, but it turned out we managed to upgrade in just about 5-6 hours! And that is without any previous serious experience with VMware! Well, yes, we have only two hosts, no cluster and just about 20-25 active virtual machines. But anyway. We had some problems on our way, but generally installation was not that complicated.</p>
]]></content:encoded>
			<wfw:commentRss>http://maksim.sorokin.dk/it/2010/02/26/how-we-upgraded-our-vmware/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

