>>29
I believe they're talking about vanilla ANSI C's standard library. On any modern platform, C is capable of threading, networking, exceptin handling, and many other things, in non-standard, but well documented(extensions) ways. Effectively, you can do practically anything imaginable with third party libraries or libraries you build yourself, they're just not standardized.
This is a fairly common type of whining present in many languages which have been standardized in one form or the other. For example, Common Lisp is sntadardized and has a pretty rich standard library, but at that time threading, networking, FFI were not considered things on which people could agree on a common ground or were considered things which would reduce the chance of portability of the language to all kinds of obscure platforms, so they were never included in the standard. Now you see people say/whine that you can't do all kinds of low-level things in CL, when you have de-facto portable libraries for doing FFI, threading, networking. (De-facto means that someone spent some time to write a thin portability layer on top of whatever many of the popular implementations probide under the hood(documented) for doing these kinds of things). Practically, you can write your code using these libraries and achieve full portability, but people will still while because it's not engraved in the golden standard that every implementation must obey, lest they be deemed non-conforming.