4 ms·
They managed to write an entire article about POSIX and never mention the filesystem parts? Even the section about "asynchronous I/O" seems to have more to do
by notacoward 10y ago
They managed to write an entire article about POSIX and never mention the filesystem parts? Even the section about "asynchronous I/O" seems to have more to do with locking than actual I/O. Nothing about directory operations, permission models, consistency/durability requirements, and all the other things that make that part of POSIX the most egregiously out of date. I wrote a bit about this (http://pl.atyp.us/2016-05-updating-posix.html http://pl.atyp.us/2016-05-updating-posix.html) and barely scratched the surface. I wish they'd dared to go there too.
- JdeBP 10y agoThere's a whole lot of POSIX that they didn't mention. They concentrated upon the system call API and left out all of the concepts (character sets, locale, environment variables, regular expressions, command line conventions), the filesystem, the shell, and the utilities.
- notacoward 10y agoThey didn't even cover the system call API.
- gens 10y agoYep, only libc. And only for some popularly installed (after system install) programs. >We selected these apps from the official marketplaces for each OS: Google Play (45 apps), Apple AppStore (10 apps), and Ubuntu Software Center (45 apps). We chose popular apps based on the number of installs, selecting apps across nine categories, .. So mostly GUI programs. Not to mention that probably all those "apps" call into libc eventually (even android ones). Only thing this made me think about is "why is this taken seriously here?".