Pure Bash Bible
github.com
Pure Bash Bible
1–10 of 258 posts
Re: Pure Bash Bible
#2I expected a tool on bash where you can access the pure "Bible"
hallelujah.sh
Re: Pure Bash Bible
#3no mention of /dev/tcp?!
yes, it looks like a device node in /dev, but it's really a pure bashism for opening tcp connections to arbitrary hosts and ports
Re: Pure Bash Bible
#4While this is interesting I see doing anything but launching programs with simple text-substituted arguments as too much for bash or sh. Run shellcheck on some of your own code, or the code of even a simple project to see how hard it is to really use bash.
Why I think people gravitate towards it is because languages such as python add too much pomp to launching a shell process. A language like perl is usually easier to use but everyone hates it now.
Re: Pure Bash Bible
#5[deleted]
Re: Pure Bash Bible
#6Kinda cool, I don’t write or read much bash and tend to stick to sh compatible stuff.
There are some neat tricks in here but they don’t seem very readable compared to perl/awk/sed.
Re: Pure Bash Bible
#7Neat. Sometimes bash is the right choice, and then a guide like this is a great complement to google / stackexchange.
Re: Pure Bash Bible
#8no mention of /dev/tcp?! yes, it looks like a device node in /dev, but it's really a pure bashism for opening tcp connections to arbitrary hosts and ports
Whoa... News to me! Thanks.
Re: Pure Bash Bible
#9Didn't realize at first that "pure" refers to features available in bash without calling out to external processes, when I would've thought purism in this context should refer to avoiding bashisms and writing portable (ksh, POSIX shell) scripts.
Re: Pure Bash Bible
#10While this is interesting I see doing anything but launching programs with simple text-substituted arguments as too much for bash or sh. Run shellcheck on some of your own code, or the code of even a simple project to see how hard it is to really use bash. Why I think people gravitate towards it is because languages such as python add too much pomp to launching a shell process. A language like perl is usually easier…
> I see doing anything but launching programs with simple text-substituted arguments as too much for bash or sh
I would heartily agree. If your shell script grows beyond half a dozen commands or so, you're probably better off rewriting it in just about anything. Python, ruby, go (gorun), rust (cargo-script), or whatever else, doesn't really matter as long as it's not shell.