[afiori]

I want to add something to this: abandoning the fire layer allows for richer custom flows (which to many are arguably worse)

For example the file API does not allow a clean, uniform, and reliable way to associate a resource with some metadata

[palata]

I don't get that. How do you expect to abandon the file layer on your OS? Do you plan on rewriting Windows, macOS, Linux, Android and iOS with a fundamentally new philosophy?

If not, then you're not abandoning the file layer at all. You're just preventing people from benefitting from it.

[kmarc]

The file API might not, but all major filesystems implemented some kind off Metadata attributes, IIRC Microsoft was wanting to heavily rely on that for "user space" stuff (e.g. Users leveraging it for semantic information about their files)

[ddingus]

If we don't have files, then what?

Seems to me we very rapidly arrive at records or entities.

We see both these days in databases.

Entities show up in CAD and simulation. Records show up in business tools of various kinds.

All require a schema and serious dependencies flow from there.

In CAD, for example, the database schema can change quite dramatically from version to version of the same software tool. And all this makes writing plug in tools or anything really painful.

And forget exchanging native data between systems. STEP exists for that, and O God help you on a bigger project involving any old data

The thing about files is they are basically EASY.

And easy, when looking at where we are going, matters. A lot.

Files can exist on pretty much anything. Paper tape, mag tape, all sorts of media, up to advanced storage tech.

Databases are a different story.

I am not convinced we are anywhere rear being ready for that huge leap.

And I would normally say "forward" but on this?

Nope!

It would be a huge mess requiring we toss just about everything we have in use today