News for hackers. Stuff that matters.
Re:Linus on btime: “Let’s wait five years” (2010) by guessmyname on Thursday September 22, 2016 @08:53AM (#12556447)
Off Topic — Which one is better?

    $ stat `which stat`
    $ stat $(which stat)
Re:Linus on btime: “Let’s wait five years” (2010) by hmpc on Thursday September 22, 2016 @09:04AM (#12556511)
Backticks are discouraged for any new scripts, since they complicate nesting, quoting, and escaping, besides being graphically less explicit. See also http://mywiki.wooledge.org/BashFAQ/082. The Open Group also discourages backticks: http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xcu_....
Re:Linus on btime: “Let’s wait five years” (2010) by __michaelg on Thursday September 22, 2016 @09:11AM (#12556556)

    $ stat "$(which stat)"

shellcheck or its online version http://www.shellcheck.net/ help a lot
Re:Linus on btime: “Let’s wait five years” (2010) by striking on Thursday September 22, 2016 @08:57AM (#12556472)
Backticks if lazy, parenthetical for complicated command lines.
Re:Linus on btime: “Let’s wait five years” (2010) by andrewSC on Thursday September 22, 2016 @09:11AM (#12556551)
Haha, I read that as "...complicated command times."
Re:Linus on btime: “Let’s wait five years” (2010) by striking on Thursday September 22, 2016 @09:17AM (#12556593)
Close enough!
Re:Linus on btime: “Let’s wait five years” (2010) by aelleth on Thursday September 22, 2016 @09:23AM (#12556627)
$(...) doesn't trip Shellcheck and is slightly more readable and less error-prone in complex statements, e.g. if you have to nest commands.
Re:Linus on btime: “Let’s wait five years” (2010) by rascul on Thursday September 22, 2016 @09:47AM (#12556764)
which probably isn't the best tool to use here.

http://unix.stackexchange.com/questions/85249/why-not-use-wh...