zlacker

>>jsnell+(OP)
It's interesting that this is almost entirely about the filesystem API, but barely touches on all the other things that the object-store proponents and other "POSIX is dead" advocates usually focus on. Hierarchical directory structure, byte addressability, write in place, permissions model, persistence and consistency requirements, and so on. If everybody switched to a new API today, POSIX would still be very much alive. I'm not going to argue about whether the rest of POSIX should die or not, having played an active role in such discussions for about twenty years, but for that to happen it has to be a lot more than just changing how requests and responses are communicated.

>>notaco+yi
Cloud computing runtimes and serverless.

They can be running bare metal on top of a type 1 hypervisor, on top of a UNIX, Windows, mainframe, micro, or whatever.

Android and ChromeOS, which although based on the Linux kernel, don't expose a POSIX userspace to regular app developers as public API, only OEMs get to play with it, or placing the devices into developer mode like Crostini.

It doesn't matter at all on the XBox and Nintendo, but it does on PlayStation.

Its relevancy depends pretty much how deep one still is into classical UNIX like workflows, but like COBOL and Fortran it isn't going away anytime soon.

Unysis still sells Burroughs as well.

>>pjmlp+Pl
>which although based on the Linux kernel, don't expose a POSIX userspace to regular app developers as public API

No, Android apps can contain native code that uses Linux syscalls.