3 ms·

How this compares to busybox[1]? Additional functionality? I would rather stick to posix/unix commands than learn a new list of new functions [1]: https://www

How this compares to busybox[1]? Additional functionality? I would rather stick to posix/unix commands than learn a new list of new functions [1]: https://www.busybox.net/ https://www.busybox.net/

saagarjha 6y ago
This seems to be cross-platform, while BusyBox is mostly Linux-only.
- 1vuio0pswjnm7 6y ago
  "Mostly". I recall trying a BusyBox from FreeBSD ports. Seemed sorta like a gimmick. Not really needed. Wikipedia confirms my memory. https://en.wikipedia.org/wiki/BusyBox https://en.wikipedia.org/wiki/BusyBox
- augusto-moura 6y ago
  Busybox only gives full support for Linux, but can be and is frequently compile for a lot of operating systems, including Windows that is not a *nix per se and also embedded systems
interfixus 6y ago
Completely different beasts. Busybox is a tight, lightweight implementation of [a subset of] the Posix toolchain. This thing - also tight and lightweight - is a collection of commands primarily geared towards manipulation of file names and contents. Highly un-unixy (more like "do all sorts of things and do them well") but with clear, straightforward, non-arcane syntacs. I had a pile of somewhat complex text transformations I needed to perform, and was getting headaches just contemplating the hodge-podge of cat and grep and find and awk and sed and regex and stackoverflow and kilometers of pipes I would be getting into, not being much of a wizard with such things, so went looking for something a bit less daunting. Found this, and within in an hour had a working script which I am fairly certain I will also be able to read and understand a year from now.
- augusto-moura 6y ago
  Got it. Even so I still prefer to learn only unix and go with it, most of the time awk solves all my data problems About your transformation problems, give a look at NuShell[1], it's a full fledged shell but I rarely use it as a interactive shell, mostly as a scripting language, it heavily simplifies the extract, transform and load from the terminal. Also it's written in Rust and available to most mainstream OSes [1]: https://www.nushell.sh/ https://www.nushell.sh/
JdeBP 6y ago
It's very similar, except that its heritage is clearly the world of MS/PC/DR-DOS style toolsets rather than Unix toolsets. It's a multiple-function binary, with freely licensed source code, that basically provides a whole bunch of otherwise standalone tools in one. The difference is that the standalone tools have the sorts of semantics that will be very familiar to people who lived through the times of MS/PC/DR-DOS shareware, where there were (and still are) loads of tools in this vein, both standalone and all-in-one. Both minus and plus are command-line switch characters. There's no special GNU-style marker for "long" options to differentiate them from "short" options. Command names and functions follow conventions that were more common in the MS/PC/DR-DOS shareware world (e.g. DELTREE, HEXTOBIN, HEXDUMP, COLOR, FIND). And PC-isms like the idea that there are 16 CGA colours are baked in (c.f. this toolset's ECHO command). If you've used the Norton Utilities, the Graham Utilities, JP Software's 4DOS/4OS2/4NT, my OS/2 (and earlier DOS) Command Line Utilities, or any of the many implementations of commands such as DELTREE that were available, this sort of thing is very familiar and comfortable territory. * https://jpsoft.com/help/tcc_and_tcclite.htm https://jpsoft.com/help/tcc_and_tcclite.htm * http://www.warpspeed.com.au/Products/OS2/GU/graham.htm http://www.warpspeed.com.au/Products/OS2/GU/graham.htm * http://jdebp.uk./Softwares/clu.html http://jdebp.uk./Softwares/clu.html * https://hobbes.nmsu.edu/?dir=/&stype=all&sort=type_name&search=deltree https://hobbes.nmsu.edu/?dir=/&stype=all&sort=type_name&sear...

How this compares to busybox[1]? Additional functionality? I would rather stick to posix/unix commands than learn a new list of new functions [1]: https://www.busybox.net/ https://www.busybox.net/

saagarjha 6y ago

This seems to be cross-platform, while BusyBox is mostly Linux-only.

1vuio0pswjnm7 6y ago
"Mostly". I recall trying a BusyBox from FreeBSD ports. Seemed sorta like a gimmick. Not really needed. Wikipedia confirms my memory. https://en.wikipedia.org/wiki/BusyBox https://en.wikipedia.org/wiki/BusyBox
augusto-moura 6y ago
Busybox only gives full support for Linux, but can be and is frequently compile for a lot of operating systems, including Windows that is not a *nix per se and also embedded systems

interfixus 6y ago

Completely different beasts. Busybox is a tight, lightweight implementation of [a subset of] the Posix toolchain. This thing - also tight and lightweight - is a collection of commands primarily geared towards manipulation of file names and contents. Highly un-unixy (more like "do all sorts of things and do them well") but with clear, straightforward, non-arcane syntacs. I had a pile of somewhat complex text transformations I needed to perform, and was getting headaches just contemplating the hodge-podge of cat and grep and find and awk and sed and regex and stackoverflow and kilometers of pipes I would be getting into, not being much of a wizard with such things, so went looking for something a bit less daunting. Found this, and within in an hour had a working script which I am fairly certain I will also be able to read and understand a year from now.

augusto-moura 6y ago
Got it. Even so I still prefer to learn only unix and go with it, most of the time awk solves all my data problems About your transformation problems, give a look at NuShell[1], it's a full fledged shell but I rarely use it as a interactive shell, mostly as a scripting language, it heavily simplifies the extract, transform and load from the terminal. Also it's written in Rust and available to most mainstream OSes [1]: https://www.nushell.sh/ https://www.nushell.sh/

JdeBP 6y ago

It's very similar, except that its heritage is clearly the world of MS/PC/DR-DOS style toolsets rather than Unix toolsets. It's a multiple-function binary, with freely licensed source code, that basically provides a whole bunch of otherwise standalone tools in one. The difference is that the standalone tools have the sorts of semantics that will be very familiar to people who lived through the times of MS/PC/DR-DOS shareware, where there were (and still are) loads of tools in this vein, both standalone and all-in-one. Both minus and plus are command-line switch characters. There's no special GNU-style marker for "long" options to differentiate them from "short" options. Command names and functions follow conventions that were more common in the MS/PC/DR-DOS shareware world (e.g. DELTREE, HEXTOBIN, HEXDUMP, COLOR, FIND). And PC-isms like the idea that there are 16 CGA colours are baked in (c.f. this toolset's ECHO command). If you've used the Norton Utilities, the Graham Utilities, JP Software's 4DOS/4OS2/4NT, my OS/2 (and earlier DOS) Command Line Utilities, or any of the many implementations of commands such as DELTREE that were available, this sort of thing is very familiar and comfortable territory. * https://jpsoft.com/help/tcc_and_tcclite.htm https://jpsoft.com/help/tcc_and_tcclite.htm * http://www.warpspeed.com.au/Products/OS2/GU/graham.htm http://www.warpspeed.com.au/Products/OS2/GU/graham.htm * http://jdebp.uk./Softwares/clu.html http://jdebp.uk./Softwares/clu.html * https://hobbes.nmsu.edu/?dir=/&stype=all&sort=type_name&search=deltree https://hobbes.nmsu.edu/?dir=/&stype=all&sort=type_name&sear...