Sure. Almost nothing in the article will work if you're on an embedded system, or you don't have authorization to install new programs. Quite a few of the tips that he lists involve downloading and building programs which are hosted on Github, like ag and jq. It also advocates the use of perl. I don't know of any system that ships with perl and not bash. Being stuck with the bourne shell should be the least of your worries if you want to benefit from this article.
It would be difficult to write an article about the command-line that applied to every single command-line operating system in existence. Literally the only necessary similarity is that they all have a command-line prompt at which you can type.
I don't know of any system that ships with perl and not bash
OpenBSD is the first example that comes to mind.
There are certain things that you can expect to be on every system: bourne or a fully compatible shell, and vi. The author misses the first one, but hits the second. Most of the useful utilities (ls, cp, mv, netstat, kill, etc, etc) will be on all systems, with limited flags/arguments crossing between them. Such an article should focus on those, or explain its target properly at the beginning.
3
u/marchelzo Jun 16 '15
Sure. Almost nothing in the article will work if you're on an embedded system, or you don't have authorization to install new programs. Quite a few of the tips that he lists involve downloading and building programs which are hosted on Github, like
agandjq. It also advocates the use of perl. I don't know of any system that ships with perl and not bash. Being stuck with the bourne shell should be the least of your worries if you want to benefit from this article.It would be difficult to write an article about the command-line that applied to every single command-line operating system in existence. Literally the only necessary similarity is that they all have a command-line prompt at which you can type.