'Type Manager' The File Manager of Tomorrow?
IceFox writes "In the past few years many of us have been introduced to a new type of application, the Type Manager. Most of us are familiar with iTunes, but there are many other Type Managers out there that are gaining market share and a rabid fan base of users such as digiKam and amaroK. Type Managers seem to have that magic combinations of features that makes users love them. I have been taken a closer look at the Type Manager, what makes them so usefull, what they really provide for the user and came to some surprising results. After creating a list of all the traits of a Type Manager I was able to define exactly what a file manager should be and discovered that there are in fact many partial Type Managers out there now that implemented only half of what makes up a full Type Manager."
Move along, nothing to see here. This is nothing but shameless self-promotion from a guy who can't even spell "useful" correctly.
Adobe Type Manager Light
Next time, check prior art before appropriating a phrase and giving it whatever meaning you feel like.
Not to mention, "Type Manager" is a terrible name for "application that manages files of some type".
A couple of pages of rambling is far from "news". This might be an interesting read for someone who has never thought of content or contextual organization before, but it's really old hat.
Now, if this goober had coded up a new manager which integrated all the functions he talked about, or had an extensble base manager to replace the native file system, with a defined api for plugins that would allow you to customize the environment, that would be news.
Is it just my observation, or are there way too many stupid people in the world?
You don't just start using it as if it's already known. You have to first "propose" the definition at the beginning of the paper and explain why you're using it.
The only difference between a file path and, say, keywords is that the former is thinking in terms of the computer (sort of like C), whereas the latter is thinking in terms of the data (sort of like Java).
That's wrong. Paths are not just metadata, they have specific semantics associated with them that, say, tags don't. Furthermore, paths have semantics that users grasp easily and that they rely on.
Now, people have been attempting tag-based, non-hierarchical, database-based and other file management and navigation strategies since the 1960's. UNIX itself used to be graph-based, not path-based. All such attempts have been failures. Paths seem to combine power, usability, and correct semantics in a way that no other system has managed to do to date. There are specific applications (like MP3 jukeboxes) where other approaches are better, but for organizing all the stuff on a computer as a whole, sooner or later, you end up with paths and path semantics again.
What applications are you talking about? Word wouldn't even qualify as defined by the article. In fact specifically lists Word as a different type of application called Content Creators. The article then lists ones that would apply: iTunes, iPhoto, Juk, Amarok, and digiKam. none of which I would say are used because of their ability to share with others (even though they can contain the ability).
Seriously what applications are you talking about. Certainly not the same applications as the article.