[klmr]

> but what has this to do with storage systems?

The article is about POSIX compliance (or lack thereof) of storage systems.

And the article does not imply that “POSIX … sucks”. On the contrary: the answer to the rhetoric question in the title is obviously “no”.

> It's almost always a better idea … to write your own thin specialized glue layer between your application code and operating system APIs.

Oh, definitely. But writing good abstractions that work equally well with POSIX-compliant filesystems and with object storage is basically impossible without massive trade-offs. That’s the entire point of the product that’s advertised here: it provides a link between object storage and POSIX-compliant file access that manages these trade-offs extremely well, and it allows users to use their existing glue code for POSIX without having to deal with object storage altogether.

(COI disclaimer: I used to work on this product; but I no longer have any stakes in it, financial or otherwise.)