What's the difference between $(…) and `…`

Question

The question is as simple as stated in the title: What\'s the difference between the following two expressions?

$(...)
`...`

For example, a

Answer 1

Using ``` is the historical syntax, POSIX has adopted the now standard ` $(...) syntax. See Section 2.6.3

Answer 2

The result is the same, but the newer $() syntax is far clearer and easier to read. At least doubly so when trying to nest. Nesting is not easy with the old syntax, but works fine with the new.

Compare:

$ echo $(ls $(pwd))

versus:

$ echo `ls \`pwd\``

You need to escape the embedded backticks, so it's quite a lot more complicated to both type and read.

According to this page, there is at least one minor difference in how they treat embedded double backslashes.

Answer 3

You might want to read man bash:

When the old-style backquote form of substitution is used, backslash retains its literal meaning except when followed by $, `, or . The first backquote not preceded by a backslash terminates the command substitution. When using the $(command) form, all characters between the parentheses make up the command; none are treated specially.

That's under the "Command Substitution" section of the manpage.