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.

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 " "

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

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

Link from the homepage: https://openipc.org/supported-hardware/featured

This is a list of SOCs, not a list of devices containing these SOCs.

And for most cameras sold, you'll have a hard time figuring out pre-buy, what SOC it contains.

I'm happy for anyone who can make a use out of it, and it's nice to see one of the only examples where non-US users are ahead of the US, but…

Do you have any Amazon ASIN for any of these products, available for sale in the US?

There's a whole bunch of random no-name IP cameras available on Amazon US, often costing as low as $15 USD, possibly because some of them are subsidised by their cloud offerings, but I've never seen any of these brands listed on OpenIPC. I'm sure some of the brands we see, are simply whitelabels, but, how do you figure these things out, without a disassembly to look at the boards?

This is really good! Thanks!

But then... One of those engineers quit and another one becomes seriously ill and cannot work for a longer period of time...

Spoken like management, ha ha.

It happens. People step in and take over. The company continues.

I would believe this is mostly due to panic rather than being stupid. At some point, for many people, your logical brain stops working.

I think it's a lack of panic that does it. In that moment they're afraid of causing property damage and they aren't thinking about their own imminent demise. Probably because they see the gate before they see the train, and once they start thinking about the gate in front of them they get tunnel vision and struggle to switch focus to the more important thing coming at them from the side.

Isn't contiki-ng another one?

I've built dew for this. It "knows" about many of those apps (and where to get a container from). https://github.com/efrecon/dew. Adding a term app is usually just a matter of crafting an .env file with the necessary settings.

That's really cool

Or better : use the --wrap option so it gets clearer that no wrapping on long lines happens .

This is exactly what the article suggests.

I think they mean use "--wrap=0" instead of "-w0" as it's a little better self-documenting for those who come across your script.

In general I always try to use the long-form options in scripts as readability is more important that conciseness.

The article notes this was not possible in their specific context, as only the short form is implemented in busybox.

The commit that they have a screenshot of notes this, but it isn't in the article text. FWIW I can't read that screenshot with zoom level 100% on my desktop, but I can if I zoom further or open it in a new window (it isn't clickable though).

That's what I meant indeed. The article never mentions busybox in the text, does it?

I use ble.sh. I find it really good, even if a bit sluggish at times. The multi-line editing mode is god's end when trying little advanced snippets of shell.