The author the library expressed the sentiment that the discovery of C libraries is "relatively poor" and sometimes they are unfocused and have a bigger than necessary footprint.
The point of CLibs is to use micro-libraries that meet your project's needs. Yes, a simple Google search might suffice for a bigger project, but for the search of smaller libraries, it might not.
Personally, I don't use CLibs, mainly because I only have one project in C. The reason I made this post is so that other people would know about and perhaps some of them would find a use for it.
You didn’t answer my question.
The author the library expressed the sentiment that the discovery of C libraries is "relatively poor" and sometimes they are unfocused and have a bigger than necessary footprint.
The point of CLibs is to use micro-libraries that meet your project's needs. Yes, a simple Google search might suffice for a bigger project, but for the search of smaller libraries, it might not.
Personally, I don't use CLibs, mainly because I only have one project in C. The reason I made this post is so that other people would know about and perhaps some of them would find a use for it.
Still, what does it do to make discovery easier?
Just by using
clib search [package-name]. Sure, you could Google search it, but, it might not come up.But you still need to know about the library to do that, so it’s more of a “Can I install this through CLibs?” thing.
Sure. If you want to, Google can be a great place to find certain libraries and for others, it might not be.
There's nothing wrong with wanting to use Google for this purpose, it's just that CLibs can offer another channel for finding useful libraries.
Now you’re basically just repeating yourself.
Sorry, but that's all I have to say in this discussion. Use Google if you want and CLibs for an extra avenue for finding libraries.