cm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agoLike programming in bashimagemessage-square164fedilinkarrow-up11arrow-down10cross-posted to: programmerhumor@lemmy.ml
arrow-up11arrow-down1imageLike programming in bashcm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agomessage-square164fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squareirelephant [he/him]🍭@lemm.eelinkfedilinkEnglisharrow-up0·1 day agoIt seems like it does stuff differently for the sake of it being different.
minus-square_stranger_@lemmy.worldlinkfedilinkarrow-up0·1 day agoIt’s more like bash did it one way and everyone who came after decided that was terrible and should be done a different way (for good reason). Looking right at you -eq and your weird ass syntax if [[ $x -eq $y ]]
minus-squareAppoxo@lemmy.dbzer0.comlinkfedilinkarrow-up0·1 day agoYou better not look at powershell in that case :p
minus-squareirelephant [he/him]🍭@lemm.eelinkfedilinkEnglisharrow-up0·edit-21 day agoThat was the point where I closed the bash tutorial I was on, and decided to just use python and subprocess.run()
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up0·1 day ago -eq Yeah, like infix, so between operands, but dashed like a flag so should come before arguments. Very odd.
It seems like it does stuff differently for the sake of it being different.
It’s more like bash did it one way and everyone who came after decided that was terrible and should be done a different way (for good reason).
Looking right at you -eq and your weird ass syntax
if [[ $x -eq $y ]]You better not look at powershell in that case :p
That was the point where I closed the bash tutorial I was on, and decided to just use python and
subprocess.run()Yeah, like infix, so between operands, but dashed like a flag so should come before arguments. Very odd.