7 ms·
> This is done because the filesystem user model is inadequate or inappropriate, or because the storage model is expected to change. This is a weak analysis. I
by rektide 5y ago
> This is done because the filesystem user model is inadequate or inappropriate, or because the storage model is expected to change.
This is a weak analysis. I agree reasonably with your overall point, that this isn't entirely iOS's fault. But I see no evidence or cause to believe any of the alternate anti-file approaches have anything better to offer, present better. You yourself argue that better interfaces are presentable atop the filesystem interface, so it's obviously not a limiting factor in data-representation & data-modelling.
Rather, to me, I see cloudification requiring adaption. Files didn't apply, weren't connected, where-as the digital entities we we began trying to work with were connected, cross-system. That doesn't outmode the filesystem, but it does require adaption & reconsideration. It requires connecting. It requires going further.
I'd point out that we have no replacement for the filesystem. There's no words, no descriptor we can use to describe the alternate, the pervasive, cloudy objects that we interact with everywhere. There's nothing generic, or user-manageable that's replaced the idea of the file.
Files were a convenient reification of the digital to sacrifice, to make computing harder, and because we didn't know how to make the notion of a file more online.
- zepto 5y ago> But I see no evidence or cause to believe any of the alternate anti-file approaches have anything better to offer, present better. I think it’s fairly clear that the iOS photos app is easier to navigate than a folder with tens of thousands of files. Even the notes app presents the notes in a more useful way than a folder would. Other obvious examples are things like notion or roam research, or any number of systems where the file metaphor just isn’t natural. Many people today use a web browser to view pages of text and multimedia connected via hyperlinks. This technology hides the underlying implementation which may be files, or may be databases or other kinds of store. It is more successful than the earlier file based protocols such as FTP and Gopher. > I'd point out that we have no replacement for the filesystem. It’s not clear what this is supposed to mean. We have many other kinds of data store, e.g. relational databases, graph database, time series databases etc.
- rektide 5y ago>> I'd point out that we have no replacement for the filesystem. > It’s not clear what this is supposed to mean. i was super clear. what else have we presented users as a consistent cross system abstraction/means to handle data? nothing. you have nothing. i dont understand your arguments on ios photos or notes. google photos is one big folder full of files, and some photos can be tagged or organized. this would fit into either a filed symlinking paradigm or a use of extended attributes. i have zero clue ehy you think these apps are anything other than files and folders, but obfuscated.
- zepto 5y ago> i was super clear. what else have we presented users as a consistent cross system abstraction/means to handle data? nothing. you have nothing. The web. > i dont understand your arguments on ios photos or notes. google photos is one big folder full of files, and some photos can be tagged or organized. this would fit into either a filed symlinking paradigm or a use of extended attributes. i have zero clue ehy you think these apps are anything other than files and folders, but obfuscated. I have never used or mentioned Google photos. It sounds like you haven’t looked at iOS photos, which is what I mentioned. If you had you would never claim that extended attributes or symlinking would replace the experience. You also simply ignored the other examples, like notion, or roam research. None of these things are done better by simply having folders full of files. If files were better, that’s what we’d be using, since we had networked filesystems before we had the web.
- rektide 5y ago> The web. this is intangible & ungraspable. it compares in no way to files. if you think it does compare to files, explain how. chiefly i see the web as in no way offering the user-directed malleability that a personal computer has. the web never achieved the vision of writability that Tim Berners-Lee imagined. it should. but it hasn't. > None of these things are done better by simply having folders full of files. this is not what files are though. they're also symlinks and extended attributes. and again i'd argue that most every system is better when it has files under it. tools like Roam are better when there's user-manageable files underneath: the excellent open source Foam (https://foambubble.github.io/foam/ https://foambubble.github.io/foam/) does just that, and is easier to manage for it, while retaining the non-file-centric linked-web-of-documents feel that Roam/Zettlekastan-notes is known for. the alternates you cite aren't alternatives: they're all doable, easily, as files and folders. to not afford the common-man's offering for these applications is a travesty & a crime. my father greatly prefers managing photos by folders. it's the only system that has made sense to him. he's found every alternative jarring & frustrating. there's a common ground, something tangible & real about the OS having constructs & tools for managing digital things, and my dad gets it, & can use it. not being subject to each application's intangible, abstract digital entities, having "real" digital entities is empowering. > You also simply ignored the other examples, like notion, or roam research. still not sure what any of your arguments are. you cite applications but don't provide even an elementary review of how or what characteristics are different, how the experience is different. your parade of other applications is just adding more chaff. i think your analysis is weak.