Why is the MacOS file system so impossibly slow antiquated clunky and prone to failure?

Apple will not see your post here in this user to user community. You can provide feedback to Apple here: Product Feedback - Apple

etresoft wrote: Maybe it would be better if you led with the specific problem you’re having. I could rip on Apple all night long, but that wouldn’t give you any material assistance.

I would like to second etresoft, in suggesting you tell us the real problem you are trying to solve.

Because we cannot create a new file system for you, but we might be able to help if we know the problem.

Randall Lee Reetz wrote:

When will apple build a robust fast accurate safe semantically aware file system with gradual embedding and linking more like a relational database than a flat file system? Meaning, when will apple walk away from 70 year old protocols and build something robust and forward thinking?

Like WinFS, in a manner of consideration?

But then I also doubt Apple will be replacing APFS soon.

This rift between, the constant friction friction between local and remote storage is worse than embarrassing.

Having worked a whole lot with multi-server and geographically distributed shared-write clustered file systems, and shared-write relational databases, a distributed lock manager or some other scheme to provide consistency (or eventual consistency) is a central requirement, and that then brings in details such as distance becoming centrally involved in available file system performance, or the need to sidestep ACID.

And that’s before we get into the “fun” that arises within object stores.

If you want a slightly different thought project, conceptually get rid of sector addresses and I/O requests and the rest, and the whole of the I/O scheme, and ponder how a byte-addressable persistent-memory file system works, and how non-volatile main memory would work. Consider that Apple SSDs are running at main memory speeds from not that long ago (DDR3-era), for instance.

But you’ll want to log your feedback with Apple with some more specific suggestions around where APFS falls short.

The specific feedback link that you would want to use is here:

Feedback - macOS - Apple

Asking users on a Community Support site is pointless. This is not a Social Media site where speculation is allowed and no one here would have any inside knowledge of Apple future plans that have not been publicly disclosed. Anyone that would have knowledge operates under an NDA and would not be sharing that information here or anyplace else.

Randall Lee Reetz wrote:

When will apple build a robust fast accurate safe semantically aware file system with gradual embedding and linking more like a relational database than a flat file system?

Never. If there’s one thing that Apple’s particularly bad at, it’s information management.

Meaning, when will apple walk away from 70 year old protocols and build something robust and forward thinking?

You’re talking about two different things. Apple is very quick to walk away from protocols, as long as they’re useful, stable, and proven. But building something robust and forward thinking? Yeah, no.

This rift between, the constant friction friction between local and remote storage is worse than embarrassing.

Maybe it would be better if you led with the specific problem you’re having. I could rip on Apple all night long, but that wouldn’t give you any material assistance.