Closed pfi79 closed 1 month ago
@denyeart The author of this library is weakly supportive, which is what he wrote about. He himself switched to the kong library.
Perhaps we should get rid of it in fabric. Should I switch to cobra and viper, as is done in peer, or to the same kong?
From my memory kingpin was simpler than cobra, so I'd be ok leaving it on the older kingpin (no update) to keep things simple. If you really want to invest your time in an update to kong or cobra then I'd be fine with it, up to you.
@denyeart The author of this library is weakly supportive, which is what he wrote about. He himself switched to the kong library. Perhaps we should get rid of it in fabric. Should I switch to cobra and viper, as is done in peer, or to the same kong?
From my memory kingpin was simpler than cobra, so I'd be ok leaving it on the older kingpin (no update) to keep things simple. If you really want to invest your time in an update to kong or cobra then I'd be fine with it, up to you.
Okay, maybe sometime in the future.
I'd be ok leaving it on the older kingpin (no update) to keep things simple
then I'm closing the pr?
Yes, let's close the PR. The command utilities have been very stable, and the no-help
thing is confusing, let's keep current dependency.
@denyeart The author of this library is weakly supportive, which is what he wrote about. He himself switched to the kong library.
Perhaps we should get rid of it in fabric. Should I switch to cobra and viper, as is done in peer, or to the same kong?