|
|
|
|
|
by wiether
515 days ago
|
|
First of all, thank you for your work! I'm using it daily for many years now and it does exactly what I expect it to do. Now I'm a little concerned by the end of your message because it could make its usage a bit trickier... My main usecase is to curl the raw discord.sh file from GitHub in a Dockerfile and put in in /user/local/bin, so then I can _discord.sh_ anytime I need it.
Mostly used for CI images. The only constraint is to install jq if it's not already installed on the base image. Switching to Go or C would make the setup much harder I'm afraid |
|
On the concern of it would be harder to setup, I think it would be easier in fact, you would simply curl the Go or C statically generated binary to your path and would alleviate the need for jq or curl to be installed alongside.
I think the reason I haven’t made the switch yet is I like Bash (even though my script is getting pretty big), and in a way it’s a testament to what’s possible in the language. Projects like https://github.com/acmesh-official/acme.sh really show the power of Bash.
That and I think the project would need a name change, and discord.sh as a name gets the point across better than anything I can think of.