You really do not cover anything in this video. If you want to explain the differences between these two, you should cover more than just which one is most portable and have been the standard the longest. You have not covered a single feature of either of these shells. Also there are two different use cases for a shell, command line and scripting.
BASH was introduced in 1989, not 1998 lol. I'm just learning this BASH stuff, had to bust on ya, we all make simple mistakes. Awesome video none the less.
Haha, that sounded like me explaining to an old boss about NFS and saying it had been around for decades, and just because he hadn't heard of it, didn't mean it wasn't awesome.
Trick question! Bash and Zsh are command line interpreters, they are not terminals (or terminal emulators as they are called), that would be gnome-console, konsole, tilix, Eterm, etc.
True, but without a shell the terminal is basically useless. Either way, which one do you use? I use bash, but I hear a lot of people recommend zsh all the time.
@anon_y_mousse depends, I suppose. Macs defaulted to zsh because bash turned to GPLv3 so they stopped supporting it. I had previously switched to zsh on a bunch of systems to set up oh-my-zsh, but now they have oh-my-bash. Bash also has a terrible tendency to break stuff even in minor updates (I am looking at it changing == vs = in some minor update that broke some of my scripts!). Either way, I prefer them to older shells, like tcsh, ksh, etc.
@@slaapliedje Was that a comparison in an `if` change? Otherwise I don't remember that one. It's unfortunate that a lot of projects don't realize the mistake of using the GPL, but it just hurts open source in the long run.
@anon_y_mousse GPL is fine. Just a way to force people to share their changes. Yeah, the comparison changes. Older versions of Bash used == for equals, and newer dropped one.
@@slaapliedje Must've been changed over a decade ago if I can't even remember it happening, but then I don't remember most of the changes they've made. Just a few weird ones like how they create hash tables internally.
I started using zsh in the mid-90's on various Unix systems due to the much superior completion support and command line editing as compared with ksh and bash. No doubt, bash has improved over the years but zsh is still next level. These days, I'm mostly working on remote Linux servers so I leave the default shell as bash but for local use, zsh is still my preference. I don't see script compatibility as a real issue as you start off the script with #!/usr/bin/bash or #!/usr/bin/zsh as appropriate. When writing scripts, I mostly write for bash as I learned scripting pre-bash when the Bourne Shell was all that was available and it's always available on all Linux distributions.
first I used bash, then I tried zsh...got hooked up for some time. Then I accidentally deleted my .zshrc but some of it got duplicated in .bashrc Then i tried using bash with all the plugins to make it behave liks zsh...i can't. End up rewriting my .zshrc which include several hundreds lines of code!
Have you heard of and maybe used qbsh? It's a QBasic-based shell, as in it's written in a variant of QBasic that compiles with qb64 and it interprets some BASIC commands. If you haven't, then there's a video idea for you.
arch ? the thing for people who aren't able to install gentoo ? 😋 just a starship prompt over my shell so i have the same interface when i'm on windows, linux and mac ^^
I just find there's not enough compelling me to make the switch. The main reason I want to learn zsh at some point (when I'm done with Rust and Awk) is that macos uses zsh as its default shell. For now I have bash installed via ports, and a script which takes all my bash scripts from my Linux machines, and changes the #! of the script to point to /opt/local/bin/bash instead of /bin/bash. I learned the basics of bash in the 90s, (I first discovered Linux early 1996), and it's one of those things, like vim, that once you've learned it once, there is little needed by way of re-learning.
9 หลายเดือนก่อน
zsh is superior because he has left-side fork in pipes instead of right-side fork. Try that in bash: $ echo a | read b ; echo $b $ and then in zsh: $ echo a | read b ; echo $b a $
@@ErikOnNoobTube Of course, as another user already pointed out, the shebang negates all arguments as to what shell you should use personally as long as you have the standard installed.
If zsh had better plugin api then i would use it, but writing widgets / keybinding functions on bash is a pain in the arse oh-my-zsh is a horrible piece of software that slows everything down a lot and i would never recommend to use it unless you know what it does (and it does A LOT of things like aliases and settings)
@@Felix-ve9hstried it for a week but didn't like it. I think its main selling point is a more structured i/o. For example: running ls returns a table and don't need to parse output to extract info Something like powershell in windows
You really do not cover anything in this video. If you want to explain the differences between these two, you should cover more than just which one is most portable and have been the standard the longest. You have not covered a single feature of either of these shells. Also there are two different use cases for a shell, command line and scripting.
but is prosody is perfect for helping you falling asleep; so overall it's a great video... ...if you plan to have a nap 🤣😂
BASH was introduced in 1989, not 1998 lol. I'm just learning this BASH stuff, had to bust on ya, we all make simple mistakes. Awesome video none the less.
Haha, that sounded like me explaining to an old boss about NFS and saying it had been around for decades, and just because he hadn't heard of it, didn't mean it wasn't awesome.
Trick question! Bash and Zsh are command line interpreters, they are not terminals (or terminal emulators as they are called), that would be gnome-console, konsole, tilix, Eterm, etc.
True, but without a shell the terminal is basically useless. Either way, which one do you use? I use bash, but I hear a lot of people recommend zsh all the time.
@anon_y_mousse depends, I suppose. Macs defaulted to zsh because bash turned to GPLv3 so they stopped supporting it. I had previously switched to zsh on a bunch of systems to set up oh-my-zsh, but now they have oh-my-bash. Bash also has a terrible tendency to break stuff even in minor updates (I am looking at it changing == vs = in some minor update that broke some of my scripts!). Either way, I prefer them to older shells, like tcsh, ksh, etc.
@@slaapliedje Was that a comparison in an `if` change? Otherwise I don't remember that one. It's unfortunate that a lot of projects don't realize the mistake of using the GPL, but it just hurts open source in the long run.
@anon_y_mousse GPL is fine. Just a way to force people to share their changes. Yeah, the comparison changes. Older versions of Bash used == for equals, and newer dropped one.
@@slaapliedje Must've been changed over a decade ago if I can't even remember it happening, but then I don't remember most of the changes they've made. Just a few weird ones like how they create hash tables internally.
What are those advanced features? That's what i hoped for when i started watching, and you didn't deliver ...
I thought everyone was using fish now.
i think fish should only be run as an interactive shell, use posix compliant shell as the login shell.
I started using zsh in the mid-90's on various Unix systems due to the much superior completion support and command line editing as compared with ksh and bash. No doubt, bash has improved over the years but zsh is still next level. These days, I'm mostly working on remote Linux servers so I leave the default shell as bash but for local use, zsh is still my preference. I don't see script compatibility as a real issue as you start off the script with #!/usr/bin/bash or #!/usr/bin/zsh as appropriate. When writing scripts, I mostly write for bash as I learned scripting pre-bash when the Bourne Shell was all that was available and it's always available on all Linux distributions.
first I used bash, then I tried zsh...got hooked up for some time. Then I accidentally deleted my .zshrc but some of it got duplicated in .bashrc
Then i tried using bash with all the plugins to make it behave liks zsh...i can't. End up rewriting my .zshrc which include several hundreds lines of code!
Guess I'll give Zsh a try since I mainly use tcsh...
Have you heard of and maybe used qbsh? It's a QBasic-based shell, as in it's written in a variant of QBasic that compiles with qb64 and it interprets some BASIC commands. If you haven't, then there's a video idea for you.
My Weapon of choice is fish. Aaaand i use Arch btw. 🙃
fish on top
Aaaand yep! Its all over the screen. DATTEBAYO, fellas! 😁👊
arch ? the thing for people who aren't able to install gentoo ? 😋
just a starship prompt over my shell so i have the same interface when i'm on windows, linux and mac ^^
I just find there's not enough compelling me to make the switch. The main reason I want to learn zsh at some point (when I'm done with Rust and Awk) is that macos uses zsh as its default shell. For now I have bash installed via ports, and a script which takes all my bash scripts from my Linux machines, and changes the #! of the script to point to /opt/local/bin/bash instead of /bin/bash. I learned the basics of bash in the 90s, (I first discovered Linux early 1996), and it's one of those things, like vim, that once you've learned it once, there is little needed by way of re-learning.
zsh is superior because he has left-side fork in pipes instead of right-side fork. Try that in bash:
$ echo a | read b ; echo $b
$
and then in zsh:
$ echo a | read b ; echo $b
a
$
Nice to know that. Thanks. I'll remember to hop into zsh when I need left-side-fork with read. It actually makes a lot of sense doing it that way.
Doesn't matter, I use fish 🎉
fish
dear lord, I thought this was one of those TTS videos before I saw the Camera....please
Fish
Both are better in a standpoint on their ground.
Yeah I totally agree.
Great content, keep it up!
Appreciate it!
bash because of teamwork and multples servers
fish shell my favorite
fish is not posix compliant though, which means i have to rewrite my sh scripts
@@ErikOnNoobTube unfortunately yea but fish is a very nice shell
@@ErikOnNoobTube Of course, as another user already pointed out, the shebang negates all arguments as to what shell you should use personally as long as you have the standard installed.
I'm allergic to shell fish
zsh wins the terminal bash wins in scripting fish is similar to zsh but it does too many things for me in terms of autocorrect
If zsh had better plugin api then i would use it, but writing widgets / keybinding functions on bash is a pain in the arse
oh-my-zsh is a horrible piece of software that slows everything down a lot and i would never recommend to use it unless you know what it does (and it does A LOT of things like aliases and settings)
pronounced "zash"
Good to know. Thanks.
Don't tell him that. He's already pronouncing "origin" [or-ih-jihn] as [o-rijin]. Don't make him pronounce something else like that.
Ha, he properly pronounces it zee esh aytch. Instead of Zed Esh Haytch.
@@asteroiderer😈
Zeesh or Zed ess aitch
nushell best shell, built with Rust
And what makes it the best shell?
@@Felix-ve9hstried it for a week but didn't like it. I think its main selling point is a more structured i/o. For example: running ls returns a table and don't need to parse output to extract info Something like powershell in windows
@@salim444 Structured output? Pfft. Who needs that when you have sed and awk.
!45 and !! don't work. Which means e.g. you can't do sudo !! like you can in bash.