What's "wrong" about the article is that the author has no idea what malloc(3) does, or about the wide range of execution environments C programs find themselve

What's "wrong" about the article is that the author has no idea what malloc(3) does, or about the wide range of execution environments C programs find themselves in and the different ways that the API maps to those environments. More generally, the article does nothing to educate the public or move the "debate" about overcommit in any sort of useful direction.