Founder here; as much as it pains many of us to hear, the vast majority of software developers never interface with <stdlib.h> directly. You can think of our choice of name more as an homage for a new generation of web-based developers.

The question we asked ourselves was --- if I'm a developer today, and I want to release services for people to easily use and compose, take advantage of new "serverless" technology, where do I put it and how do I distribute it? How do I keep my services organized? Can I build a business around an API? What does that look like?

The name "Standard Library" was a natural fit --- I consider it a huge amount of serendipity that the domain was available. We've also been lucky to have a huge amount of support from our developer community --- we got a few questions like this to begin with, which naturally caused some unease, but far more positive reactions in total. I'm very happy we've been able to build something people like. The name choice has not negatively impacted our SEO or anything like that, thankfully! :)

If you happen to play with it at all, let me know what you think!

(Humorous aside; it is more frequent for newer developers to ask us about "sexually transmitted diseases" than it is for them to get the C reference - which is totally fine, don't mind sharing knowledge! But when I told my non-CS mother about the business we were building, definitely had to really quickly explain the background of the name.)

Related story: I own stdlib.net, and have been using it for some e-mail and stuff for more than ten years. The original reason for getting it was that we were playing around with using the net.stdlib Java namespace for Apache commons. But too many people had the same reaction as you. So everything is org.apache...

hah, the C/C++ programmer in me cringed the first time I saw it. It's a decent platform though.

This name drives me a little nuts, too. The modules are named `lib`. Good luck grepping that!