# The question is
* (what is it)?
* should Nim have a vfs?
and part of answering the above question
* is it a Nim way of doing things
* if so, should it be part of stdlib or a nimble package
# What is a vfs
* packaging multiple files into an embedded or archived file (zip, tar, bzip,
....)
* keeping together all the files such as databases/configs/resources/etc for
an application or project
* simplify distribution of an application which requires multiple files
* requires a means of treating the vfs like a normal file system
* provides quasi obfuscation of files
Languages like Tcl use this methodology to package files into a single file for
distribution. The real power is making the vfs a kit, which provides a means of
executing the contents regardless of platform, so the same file can be deployed
to multiple platforms, providing a platform independent file (but this is
something more than just a vfs)
I approach this idea for Nim as meaning: "provide the means to deal with
compressed/archive files like they are just a part of the file system" (but is
this what everyone understands by a VFS?)
for example,
walkDir(/somepath/somezipfile.zip)
would walk the contents of the somezipfile.zip file as if it was some normal
directory (instead of being a compressed file)
**What do people think about this?**
