GNU coreutils does make some memory/speed tradeoffs, but all of them run great just as long as your computer has 512MiB of RAM (oh wait, you have 8 or 16 or 32 times that).
`/bin/true` will always return zero.
But unlike inferior true implementations, true will assist the user in working out what the license is as well as how to use the software, in the users native language. Behold; `/bin/true --version` true (GNU coreutils) 9.5 Copyright (C) 2024 Free Software Foundation, Inc. ライセンス GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
Your shell may have its own version of true, which usually supersedes the version described here. Please refer to your shell's documentation for details about the options it supports.
GNU coreutils のオンラインヘルプ: <https://www.gnu.org/software/coreutils/> 翻訳に関するバグは <https://translationproject.org/team/ja.html> に連絡してください。 詳細な文書 <https://www.gnu.org/software/coreutils/true> (ローカルでは info '(coreutils) true invocation' で参照可能)。
As that prints stuff to stdout, obviously that can fail, but in a script, are you going to write `/bin/true` or `/bin/true --help` to get a zero exit status .... drumroll ... you'll only ever use the former, or use GNU bash's built-in for true, which is guaranteed to return zero.
@syzygy It is correct that just an `int main() { return 0; }` is insufficiently creative to qualify for copyright law, but you should offer a free license regardless in case it does turn out that the software is restricted by copyright, so you don't end up distributing proprietary software.
I find the true implementation and how it also implements false in the same source file quite creative, so it does qualify for copyright and therefore it is licensed under the GPLv3-or-later; https://git.savannah.gnu.org/cgit/coreutils.git/tree/src/true.c