Compression Formats

Why bothering supporting all formats, when we can use single turing-complete data format and eval would be a decompressor? Then anyone could use it's own private compression algorithm.

I.e. use Lisp's lambda as compression format, then Lisp's eval would be a decoder. You can store any imaginable data inside lambdas (http://en.wikipedia.org/wiki/Church_encoding)

The file system is an artifact of the limitations of early processors that had no memory virtualization capabilities and had an insufficient memory address word size. Programs and data had to be marshalled out of and back into a logically distinct store because 64K can only hold so much information. Modern 32 and 64 bit processors with memory management units can treat storage as large, slow, persistent memory obviating the contortions required in conventional operating systems to keep data from going away when the computer is shut down.

A heirarchical name space is still required for users to keep track of where they put things but virtual memory can hold that tree structure just as well as inodes can and the judicious use of separate memory spaces can side-step a 4 gigabyte limitation for storage on 32-bit machines.