2 ms·

I know it's not what they mean and I agree with the general idea. But for very small very well contained libraries I would argue that they sometime _are_ done

I know it's not what they mean and I agree with the general idea. But for very small very well contained libraries I would argue that they sometime _are_ done (for many years, not forever; in a sense that any changes you can come up with add no relevant value at all, including no relevant perf. improvements or better maintainability). At least if written in a language with nice forward and backward compatibility, cross platform support and a stable "base" ecosystem. (So not C,C++ due to not default package manager/build system and too much divergence between platforms (e.g. unsigned long), not JS because their core build tooling changes to much (through it's getting better!), etc.)

legrande 4y ago
> But for very small very well contained libraries I would argue that they sometime _are_ done https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_and_Do_It_Well https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_a... > As stated by McIlroy, and generally accepted throughout the Unix community, Unix programs have always been expected to follow the concept of DOTADIW, or "Do One Thing And Do It Well." There are limited sources for the acronym DOTADIW on the Internet, but it is discussed at length during the development and packaging of new operating systems, especially in the Linux community.