<?xml version="1.0" encoding="utf8"?>
<rss version="0.91"><channel><title>Aeracode: Blogroll</title><link>http://aeracode.org/category/blogroll/</link><description>Posts from Aeracode, in the Blogroll category</description><lastBuildDate>Mon, 30 Oct 2006 18:51:13 -0000</lastBuildDate><item><title>Filesystem Engineering</title><link>http://aeracode.org/2006/10/30/filesystem-engineering/</link><description>More leaps and bounds (or, to give them a better name, tiny footsteps) were made with BH/e today.
The filesystem 'engine' is pretty much done now, and it's a lot better than the BH2 one. It's your standard files/folders heirarchy, but with a windows-esque separation into several top-level directories (i.e. 'Your Files', 'Andrew's Files'). There's none of the database buildup caused by bad implementation before, either, and as a plus there's folder sizes (as in actual, recursive ones) with very little processing power thanks to a gradual update system. There's even a rescan function if it all goes horribly wrong, which works quite well as well.

Now I need to start on the interface to this lot.</description></item></channel></rss>