clibs
DISCUSSION: Sub-commands as libraries with entry points
I was thinking about this issue, and my opinion is that we should compile a single binary.
Pros:
- Lot of code duplication could be removed
- Much more maintainable
- Building clib is simpler
- Solves the mentioned issue
Cons:
- Breaking change
- clib-* binaries won't be picked up as subcommands. However this could gradually removed, and replaced with a different plugin solution.
Any ideas on this?
I like the idea and could be an opportunity to really have a clean linkable C library for embedding clib or other programmatic usage. +1 for plugins
While it is a breaking change, I don't imagine many folks are leveraging the subcommand/plugin feature. There are only two plugins (listed in our registry) and I wrote both 🤣 I don't think our users would be too upset about us dropping support here.
My only concern: what would we do with the existing "plugins"? Do we just archive them? Do they provide enough value to get merged into "core"?
I think it's worth to move them to clib, and have them by default. I actually opened an issue for this #239 and I'll take a look at it soon.
Wrong button 🤦♂️
I didn't see that issue until now. Moving them into core SGTM 👍