<?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"
	>
<channel>
	<title>Comments on: You undoubtedly care nothing about Lossless Audio Servers</title>
	<atom:link href="http://www.marybicycles.com/you-undoubtedly-care-nothing-for-lossless-audio-servers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marybicycles.com/you-undoubtedly-care-nothing-for-lossless-audio-servers/</link>
	<description>“Socialism can only arrive by bicycle.” -José Antonio Viera-Gallo</description>
	<pubDate>Thu, 08 Jan 2009 12:07:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Eric Nusbaum</title>
		<link>http://www.marybicycles.com/you-undoubtedly-care-nothing-for-lossless-audio-servers/#comment-44</link>
		<dc:creator>Eric Nusbaum</dc:creator>
		<pubDate>Mon, 09 Jun 2008 21:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.marybicycles.com/you-undoubtedly-care-nothing-for-lossless-audio-servers/#comment-44</guid>
		<description>Thank you for the link and kind words! 

Because it's a frequent comment I hear on the topic, what makes .NET 3.5 a pain? I'm only curious because my experience and from what I've observed is you just install the Framework and it'll just work :)

The choice to move WWWinamp to a newer, 'managed' language was because the classic C/WinSock/Win32 API code wasn't easily scaled to support the features that I was afforded using .NET, like the ability to skin the UI to look like whatever you want (for example, our iPhone Compatible Skin). So I can understand people's desire for the 'lower overhead' of the classic WWWinamp Server, but the newer version isn't too much of a memory hog compared to todays standards (10MB with a sizable media library) and actually has many more features :)

Thanks again for the comments my way and I look forward to hearing from you! :)</description>
		<content:encoded><![CDATA[<p>Thank you for the link and kind words! </p>
<p>Because it&#8217;s a frequent comment I hear on the topic, what makes .NET 3.5 a pain? I&#8217;m only curious because my experience and from what I&#8217;ve observed is you just install the Framework and it&#8217;ll just work :)</p>
<p>The choice to move WWWinamp to a newer, &#8216;managed&#8217; language was because the classic C/WinSock/Win32 API code wasn&#8217;t easily scaled to support the features that I was afforded using .NET, like the ability to skin the UI to look like whatever you want (for example, our iPhone Compatible Skin). So I can understand people&#8217;s desire for the &#8216;lower overhead&#8217; of the classic WWWinamp Server, but the newer version isn&#8217;t too much of a memory hog compared to todays standards (10MB with a sizable media library) and actually has many more features :)</p>
<p>Thanks again for the comments my way and I look forward to hearing from you! :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
