Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Efficient string copying and concatenation in C. Parent comment
Nobody said you need to link the entire library.
Plus - with custom-made libraries, the memory footprint is no smaller.
> Easier reimplementation
Implementation begins with some part of the standard library, and gets completed gradually later on.
> Lower attack surface
Are you really arguing in favor of "everyone roll your own library" as a reduction of attack surface?
> Less room for breaking changes
C's standard library was already broken in various significant ways to begin with (e.g. gets() ...) .
Also, are you really worried about all those breaking changes between C99 and C11?
> Less baggage for when we inevitably wish we could deprecate things
Umm, you do realize things usually get deprecated when they've been replaced by something more relevant, right? In our case - new C library code.
There are no comments on this comment yet.
Nobody said you need to link the entire library.
Plus - with custom-made libraries, the memory footprint is no smaller.
> Easier reimplementation
Implementation begins with some part of the standard library, and gets completed gradually later on.
> Lower attack surface
Are you really arguing in favor of "everyone roll your own library" as a reduction of attack surface?
> Less room for breaking changes
C's standard library was already broken in various significant ways to begin with (e.g. gets() ...) .
Also, are you really worried about all those breaking changes between C99 and C11?
> Less baggage for when we inevitably wish we could deprecate things
Umm, you do realize things usually get deprecated when they've been replaced by something more relevant, right? In our case - new C library code.