Skip to content

Comment on How to write a filesystem in 50 lines of code

Comments

Intriguing. I hadn't thought of this take on filesystems before.

I'm a big fan of text-based config files but am stuck on a Windows machine at work. I wonder, would it be possible to map the registry to a virtual filesystem I could access from Explorer?

One of the many reasons to prefer PowerShell over CMD: http://powershell.com/cs/blogs/ebook/archive/2009/03/30/chap...

Nice. I'm not too into DOS, but this definitely is an easier solution than creating a VFS for the job. Thanks for the pointer.

DOS != CMD != PowerShell

I used to be a hard-core Microsoft/Windows developer; in fact, I used to work for Microsoft! I was stuck in the Visual Studio sandbox and addicted to graphical tools. It has been a very slow transition, but I'm now addicted to my shell. If you are stuck on Windows, you should force yourself to learn and use PowerShell. And at home, you should install a Unix and force yourself to learn Bash. You'll thank me later.

I mean, I'm a Unix guy so... I know bash. I don't really want to touch PowerShell or C# or .Net or anything of the kind (at work, the first thing I do is start up a Linux VM), but it's interesting to know that there is a way to treat the Windows registry as a filesystem.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.