This isn’t at all what the article is implying… this a technical analysis of the storage / usage pattern of an application.

?

Did you read the article?

Reddit is leaking into other communities.

The problem of folks responding solely to the title is not limited to Reddit. It's a pervasive thing here in HN too.

It feels good to blame reddit as we look down from our ivory towers though :)

Eh I skimmed it.

Did you read the rules?

> Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that".

Fair point.

Though I would feel a lot worse if I started commenting on the rules without having read them.

so if your user needs to know anything more than what it's in front of them; you have made bad software??? this can't be right; but I can sense my own ideological worries seeping in.

this is about a distinction between entries in a database (files) and the database itself (the filesystem is a DB).

but what's wrong with expecting people to know a little? would you argue that if the user sees the whole URL in the browser that the abstractions are leaking?

>but what's wrong with expecting people to know a little?

The issue here is that you're training users to rely on internal details.

Once users have to rely on internal details, you are stuck with maintaining these forever or face a constant stream of backlash.

This way off topic but it's an interesting question. I guess I do think the url bar is leaky. Hyperlinks are the desired abstraction, no?

The file/database in the title is more like a clickbait really. At the crux of it the author is really just talking about the granularity of the writer and reads. The article isn't advocating or commenting on the end user having to care about if it is a file or a database application.

Is your user working on a document, that is a file editor. Is your user working on a tracking system, that is a database editor.