Why a filesystem?
Why did I write a filesystem instead of writing a desktop application? Pretty simple question to answer. Because it’s not the niche I want to fit in.
There are a lot of applications already available on many platforms, including Windows, Macos X and, of course, Linux and other Unices. Those applications have wonderful graphical interfaces with lots of hints and popup, helping you getting the files tagged and getting the files back. You just apply tags and perform queries, and the files appear. You are very happy using it, until the day you want to use the same logic on the files on your office server.
Whoops, sorry, that’s impossible.
Maybe you are developing a web application which could benefit from tagging.
Whoops, sorry, that’s impossible.
And how nice would be to have this tagging logic ported to your android phone?
Whoops, sorry, that’s impossible.
Enough of those whoops? Well, then it’s time to give Tagsistant a try. Being a filesystem means that Tagsistant can be integrated in a lot of environments, since the filesystem is the most universal interface a computer knows. Some examples of environments where you can use Tagsistant right now?
- on the command line of your favorite shell
- in your favorite file manager
- in your file server managed by Samba or NFS
- in your PHP/Perl/Python/Java driven web application
- on your android smartphone (well, some hacking is required, but not too much)
Much better than a poor desktop oriented application, don’t you agree?
