4 ms·
Because it is ubiquitous. You can virtually guarantee that bash will be found on any arbitrary unix-like system.
by LeoPanthera 9y ago
Because it is ubiquitous. You can virtually guarantee that bash will be found on any arbitrary unix-like system.
- nickpsecurity 9y agoThat makes it a good idea for a compiler target for a better programming language. Not using it, though. ;)
- kazinator 9y agoSomeone thought it was a good idea to use a portable subset of the shell as a target for a worse programming language: layers of M4 macros. They didn't back away with anything like "not using it though". So now we have GNU Autotools.
- nickpsecurity 9y agoAt least the person behind that tragedy apologized in the Generation Lost in the Bazaar article's comment section. https://queue.acm.org/detail.cfm?id=2349257 https://queue.acm.org/detail.cfm?id=2349257 That one person did something damaging doesn't refute the point, though. Just avoid another M4 situation.
- deleted 9y ago[deleted]
- minikomi 9y agoSame reason I always cook my eggs using a shoe.
- xyproto 9y agoBecause a pair of shoes is always standing ready for cooking eggs in, in 99.9% of all homes?
- mihaifm 9y agoDon't make that assumption. I worked on older Solaris installations, they did have bash but the production scripts were written in ksh 88. I had to dig up obscure features of this shell in because they didn't even upgrade to the newer version ksh 93 (yes, those numbers come from their release dates...1988 and 1993).
- h1d 9y agoI keep seeing this statement but this absolutely does not apply to everybody. How often can you just install fish or use other programming language instead of being forced to use bash? It's sad people keep using the default just because of being afraid that the next system you touch might not have it and you waste tremendous amount of productivity without using something better. I know a guy who used vim with default config for that reason. Utterly nonsense.
- deleted 9y ago[deleted]
- znpy 9y agoNo one ever thinks of interoperability between people. Bash is known, to a variable depth, by pretty much every sysadmin (and a big part of being a sysadmin is being able to write shell scripts). So I might prefer the fish, and who came before me might have had a preference for zsh. So now I have to deal with three different shells: bash (default), fish (for the scripts i'll be writing from now on) and zsh (because of compatibility). Congrats. > I know a guy who used vim with default config for that reason. Utterly nonsense. I started using less and less emacs/vi(m) customization and learn more and more of the defaults for the same reason: whenever I log on a client system I am instantly proficient with the editor without stupid complaints like "but on my box is different..." . Anecdotal: I have seen people losing their editing speed/proficiency because all of a sudden they were in a clean vim session and had no one of their shiny and colorful plugins.
- h1d 9y agoWhy can you not modify the editor environment that you use often? Hard to see I need to deal with environments where I can do nothing but keep the default every time I use it. Once you get the speed that is tuned to your liking, the default sounds like you're walking with legs strapped.
- znpy 9y ago> Why can you not modify the editor environment that you use often? Because I am not the only one accessing those environments (please note the plural here). Currently there are about 13 other sysadmins in my team and we manage clients infrastructures among other things (managed services). From time to time someone from another team accesses those environment (not a sysadmin, but still familiar with the bash shell). Sometimes the client accesses those systems (rare, we try to discourage and avoid that). Can you even imagine what a mess it would be if we all started applying our own favorite settings ? (edit: fix grammar)