On 1/13/20 11:04 AM, Bernd Petrovitsch wrote:
> On 2020-01-13 15:27, Eli Schwartz wrote:
> [...]
>> The whitespace doesn't provide any value either, depending on which
>> biased analysis you'd like to make. Would this example be less wasteful
>> to you?
>>
>> ```
>> #!/bin/sh -e
>>
>> hello () { echo hello; }
>> build() { docker build -t image .; }
>> push() { docker push -t image; }
>>
>> "$@"
>> ```
> 
> "-e" doesn't buy anthing (and is not on per default) -> 3 bytes less
> Most of the ' ' are superfluous too (as it's already pretty unreadable
> anyways).
> SCNR ...

I'm not the one who initially proposed using -e ;) I'm not a fan of -e
in the first place: http://mywiki.wooledge.org/BashFAQ/105

I just reformatted whitespace for the script which was considered "too
noisy".

(But set -e would buy you something, if the script were to use command
lists. Perhaps that is what the person-who-is-not-me was thinking about...)

> [...]
>>> So, the USP here is that mim provides a very clear and intuitive
> 
> "clear and intuitive" is pretty subjective.

That is a good point as well!

> [...]
>> Couldn't you also COPY mim.sh? Why add 500 bytes to *everyone*'s
> 
> Or make it a separate package?!
> Some may have a `make` package on their small system ....

I mean, to be fair it's probably a lot easier to COPY mim.sh than get a
new package into alpine.

> [...]
>> Why must every single small script that some people consider useful, be
>> hardcoded into the busybox binary?
> 
> Because folks are too lazy to build and maintain their own small
> packages?!

And apparently they're also too lazy to check in a tiny shellscript to
their git repository, too. :/

-- 
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to