Hacker News Reader

Comment by efrecon | Hacker News Reader

Because awk understands "columns" better.

echo '999 888' | awk '{print $2}'

prints 888

How is that different from

    echo '999 888' | cut -f2 -d " "

except for the default delimiter being space for awk?

   echo '999  888' | cut -f2 -d " " # notice two consecutive spaces

returns NULL.

Right, that would be expected though? I suppose awk is better for parsing formatted (padded) output.

There are invalid column separators for awk too. To handle consecutive spaces in cut you have squeeze them:

  echo '999  888' | tr -s " " | cut -f2 -d " "

How can it be "better" when it is exactly the same?