Hacker News new | comments | show | ask | jobs | submit login

Files are a shorthand for "documents". Don't be so hung up on terminology.

First, look into history more--there are several non-hierarchical (read: flat) file systems out there.

Second, while the workflow might mirror authoring more closely (which I think is horsehit, but that's neither here nor there) the artifacts of that process are what matter. Existing notions of a "file" map very cleanly onto the storage and organization of such artifacts.

There is an argument to be made for having better querying capabilities or permissions or whatever, but what is to be gained from throwing a commonly-accepted idiom away?




There's nothing to be gained by throwing an idiom away, but maybe there's a lot to be gained with a new idiom.


There is indeed something to be gained by throwing an idiom away: not needing the features which support the idiom which create problems elsewhere, even when that idiom isn't being used.

For instance if we throw away certain programming features from a language, we can gain reliability and security which threaten even the integrity of code that doesn't itself use those features.


Butg there is the time spent in learning a new idiom, and maybe nothing is gained. Tech churn.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: