3 ms·
You know, this is all said very earnestly but the problem is that it tends to ignore the fact that many, many great things have been achieved with current techn
by chris_wot 11y ago
You know, this is all said very earnestly but the problem is that it tends to ignore the fact that many, many great things have been achieved with current technology.
The linked to "worse is better" article I have read before, years ago. The criticism of the failure mode of Unix is invalid. If you hit an error condition, then unless you have have kept your systems state for an indeterminate period of time, it's often not feasible to back out of the program to where the error occurred.
In terms of tagging, that's never taken off. Why? Because it turns out tagging things is harder than you might think, because you can call the same thing by different names, which is somewhat ironically a major problem with hierarchical file systems. You basically end up with needing to be able to locate all the tags that are synonyms of each other.
At the very least, a file system comes with a convention. I know where configuration files are on Unix - I go the the /etc directory. If I want to find my executables, I go to either /usr/bin or /bin. For my files, I'm under /home/chris.
If I was to tag stuff, I'd also need to stick to a convention, or chaos reigns. I know, I've tried this before. I basically ended up with a hierarchical tagging structure.
That's not too say tagging is awful, only that it's not a panacea to all perceived ills.
As for version control - git is honestly the best example of a versioning system that does everything you describe - content addressing, versions control, snapshots... And guess what? It's all in a DAG.
Oh, and one more thing: all that "untyped text" that is a "bad persistence model" firstly ignores the fact that it's not untyped, that every file system contains metadata, and that a file name is no different to a tag that is a label.
- blablabla123 11y ago>In terms of tagging, that's never taken off. Why? ... >because you can call the same thing by different names I guess for software packages some sort of hierarchy seems essential. At least for documents I always imagined that tags would be perfect. It seems that documents always fit in multiple hierarchies... On the other hand, if you really want no hierarchy in software packages, some standard tags are necessary. Like 'ConfigFile', 'Active', ... Also one should keep in mind that data in software is also in most cases not hierarchical. Hierarchical databases are a weird animal that nobody uses. Maybe hierarchical filesystems have constraint our minds so much that we cannot easily imagine some other way. Regarding the rest... I think as well that Unix has some problems, mostly due to old design. Having to use regexes to match file names is so error-prone, I think only for document file names that would be okay. I really like the innovative approach of Windows Power Shell eventhough the syntax is still too weird.
- chris_wot 11y agoA file system is so because it adopted the metaphor of a filing system, which was hierarchical in nature itself. It's main advantage was that it enforced order, and once you knew the filing systems you could easily locate your important records. The reason it is ubiquitous is that the human mind needs order, and a filesystem imposes this. It ain't perfect, but it works.
- blablabla123 11y agoSure, but you don't necessarily need a hierarchical order. Of course the whole desktop computer is a metaphor of the desk and the first commercially successful graphical interfaces resemble a desk. And GUIs are what most people use most of the time, even most devs tend to start their terminal from the desktop in a window, which appears a bit like paper, laying on the desk. It's interesting that only few graphical operating environments break with this convention. It seems there hasn't been much conceptual innovation in the space of "desktop computing". Even the tablet seems to represent either a piece laying on the table or the table itself, depending on the size. It should be more efficient to design systems based on the available digital infrastructure, instead of designing them based on partially obsolete office table infrastructure.
- gardano 11y agoSeems to me that what is needed is consistency. A hierarchical file systems represents something metaphorically 'physical'. A tagging system seems to me to be too ad-hoc, and therefore untrustworthy. If I know I left a file in a folder, I know it will always be there. If I tagged a file with some sort of mnemonic, then it's on me to remember what burst of inspiration told me to tag it as such.
- seagreen 11y agoYou know, this is all said very earnestly but the problem is that it tends to ignore the fact that many, many great things have been achieved with current technology. We could look at our software infrastructure as having two goals, (1) be good for experts, and (2) be good for normal people. Obviously, we're crushing it as (1). Linux, PostgreSQL, V8, GHC and so on are just disgustingly amazing feats of engineering. Nobody here is going to argue that Netflix, Google, or even your local dev shop don't do incredible work. Now let's look at (2). Normal people have a super sad relationship with computers. They can't compose one program with another (webapps aren't very good at this). They can't run a command repeatedly in an automated fashion (hard to do with a mouse). Their data is smeared across a dozen different servers, one for each webapp they use. Companies regularly do tricky things with export formats to make it hard for them to get their data back. In general, non-technical people just have an awful time. It's them we could do better by.