<?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: The One Where I Rant About Data</title>
	<atom:link href="http://www.youell.com/matt/writing/?feed=rss2&#038;p=556" rel="self" type="application/rss+xml" />
	<link>http://www.youell.com/matt/writing/?p=556</link>
	<description>simplify</description>
	<lastBuildDate>Wed, 31 Oct 2018 04:08:37 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: matt</title>
		<link>http://www.youell.com/matt/writing/?p=556&#038;cpage=1#comment-382</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Fri, 03 Dec 2010 16:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.youell.com/matt/writing/?p=556#comment-382</guid>
		<description>@Alex, I&#039;m not sure I&#039;m proposing anything in particular. This is a rant, remember.

I&#039;m tired of repackaging my data all the time. I want storage consistency between files, databases, and the network.

We&#039;re moving toward a time of RAM-as-datastore. Secondary storage is fading. The file metaphor is dated and weird. We&#039;re just used to it. Why do we keep it?

Imagine a filesystem that was a true graph. Where data didn&#039;t have to be flattened in order to be stored, or unflattened to be read. And more importantly, wouldn&#039;t lose connection to other data. That would be sweet!</description>
		<content:encoded><![CDATA[<p>@Alex, I&#8217;m not sure I&#8217;m proposing anything in particular. This is a rant, remember.</p>
<p>I&#8217;m tired of repackaging my data all the time. I want storage consistency between files, databases, and the network.</p>
<p>We&#8217;re moving toward a time of RAM-as-datastore. Secondary storage is fading. The file metaphor is dated and weird. We&#8217;re just used to it. Why do we keep it?</p>
<p>Imagine a filesystem that was a true graph. Where data didn&#8217;t have to be flattened in order to be stored, or unflattened to be read. And more importantly, wouldn&#8217;t lose connection to other data. That would be sweet!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Dodge</title>
		<link>http://www.youell.com/matt/writing/?p=556&#038;cpage=1#comment-380</link>
		<dc:creator>Alex Dodge</dc:creator>
		<pubDate>Wed, 24 Nov 2010 19:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.youell.com/matt/writing/?p=556#comment-380</guid>
		<description>I&#039;m not sure I understand what you&#039;re getting at here.  It sounds like you don&#039;t like serializing data structures.  But, that&#039;s pretty much required by current computer technology: regardless of the filesystem or file formats, hard drives store a single string of bits.  There&#039;s no way I can see to get around that, and I&#039;m still not convinced it&#039;s such a bad thing.  The alternative would be to move the structure of the data into physical space, but it seems like we&#039;d be losing a lot of flexibility with that.

What are you proposing?

Alex Dodge</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure I understand what you&#8217;re getting at here.  It sounds like you don&#8217;t like serializing data structures.  But, that&#8217;s pretty much required by current computer technology: regardless of the filesystem or file formats, hard drives store a single string of bits.  There&#8217;s no way I can see to get around that, and I&#8217;m still not convinced it&#8217;s such a bad thing.  The alternative would be to move the structure of the data into physical space, but it seems like we&#8217;d be losing a lot of flexibility with that.</p>
<p>What are you proposing?</p>
<p>Alex Dodge</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Data</title>
		<link>http://www.youell.com/matt/writing/?p=556&#038;cpage=1#comment-360</link>
		<dc:creator>Data</dc:creator>
		<pubDate>Tue, 10 Aug 2010 16:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.youell.com/matt/writing/?p=556#comment-360</guid>
		<description>Yeah man, the file metaphor in computer architecture sucks. The only thing worse is, well, the metaphor in use before the file metaphor.</description>
		<content:encoded><![CDATA[<p>Yeah man, the file metaphor in computer architecture sucks. The only thing worse is, well, the metaphor in use before the file metaphor.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
