11 ms·
The original article wasn't very good, but this response is even worse. It appears the author is lacking any form of creativity to think beyond the idea that fo
by w0utert 14y ago
The original article wasn't very good, but this response is even worse. It appears the author is lacking any form of creativity to think beyond the idea that folders are the only paradigm for ordering files that could possibly work.
In practice, if you forget about system files and such, I'd estimate 9 out of 10 people have all their documents in a single flat folder, which they only access through their word processor or whatever they use to open them. They have all their pictures and video in a tool that organizes them into albums and such without them having to deal with folders. They have all their music in a program that keeps them in a library somewhere, which they never manipulate on the file system level. And so on. Or (also very common) they just dump everything they touch on their computer on the desktop. This is not because making folders is 'too complex', but because users can't be bothered to come up with hierarchies to order where there files are 'stored on the file system' or whatever, they just want to make their changes persistent and be able to quickly find their files later.
For the vast majority of people, folders are an anochronism. It's not that they are 'hard' or 'complex', but they are simply not essential, and actually quite limiting for file management. The whole idea that the artefacts you create or consume are best structured as a tree really doesn't make a whole lot of sense. Especially not if you want to have all your data available on multiple machines which may have wildly different file systems such as desktops and mobile devices.
This doesn't mean we should all have big piles of files with no ways of structuring them, but it doesn't mean folders are the epitome of file management either. A database-like file system with powerful search options could definitely be much better. From an end-user perspective, organizing files by the applications they can open them also seems to be a pretty good idea to me. Attaching metadata and tags to files so you don't have to superimpose them using a tree-like structure would be a huge improvement.
I'm not saying that what Apple is trying with iOS and now OS X is so great we should all hail it as the future of file management, but personally I think they are moving in the right direction. Ideally, end-users should be able to operate their devices and get to their files without even knowing it has something as abstract as a 'file system'. Just sit down, get the file you want using whatever criterium makes the most sense for finding it, manipulate it, and have the same file available on every other machine. I think this is the vision Apple has, but it will take lots of time to get there.
Also, people mailing files to themselves to get them on their iOS devices literally has nothing to do with how the iOS file system works. Folders or no folders would not make any difference.
- tjoff 14y agoThen again, for many tasks, a tree truly is the best way to structure files (start broad and then home in on a file even if you have no clue about the filename or what the file contains or even the type of the file) and any file management system that doesn't recognize this is seriously flawed. I got hooked by WinFS (then again it was many many years since I last heard anything about it), a traditional filesystem with a database layer on top seems like a good start.
- w0utert 14y agoAgreed. For example trees of source code seem to fit the hierarchical structure very well, because it can (almost) map directly to projects, modules, submodules and classes, and conveniently separate them from e.g. build products or configuration files. Trees are not evil, but they are not the holy grail of file management either. From a historical point of view, a traditional filesystem with a database layer on top seems to be the most logical way to go. Personally, I think it would be interesting to see what would happen if someone did it the other way around: create a whole new way of organizing files that doesn't use trees, and allow layering some kind of 'tree view' on top of that.
- gizmo686 14y agoIf not for a specific few lines of code explicitly forbidding hard linked directories, all of the modern file systems would actually be directional graphs.
- Someone 14y agoTruly? So, what is the best way to make a hierarchy of, say MP3s: - year-performer-composer-star rating - genre-year-song title - album title-song title - ... You get the same problem almost everywhere. Is it year-project or project-year or maybe customer-year-quarter-project? Yes, for many tasks, a tree is a good way to structure information. The problem is that the choice of tree can be widely different for different tasks (for example, 'that song you played last week', 'that minute-long guitar riff by X') I think a hierarchy should be like an index in a database: set by an expert to match the most common access pattern, but not enforcing other access patterns. Hierarchical file systems are good at the former, but atrocious at the latter. And we sort-of already have WinFS, in the form of full-text indexes on file systems.