Hello!
I've found onine is pretty decent video tutorial about BASH. But it's dated around 2010. I think Ubuntu 10.10 or so... You think I can still learn today by using that old tutorial or there're changes in BASH in last years that render that course obsolete?

well if it is a video and free to watch etc.. I am sure you can pick up some good information on it. I and a lot of others are still using https://www.tldp.org/LDP/abs/html/index.html dated 10 Mar 2014

don't forget
https://mywiki.wooledge.org/BashGuide


and if you link the video we could provide feedback on it

Thank you all... Well, that video course isn't even in English :-)

what about sub titles? bash code in the video
or
what you never watched a Bollywood video and tried to figure it out?

YouTube too would be a good source if you like having to wait for the person to get to the point, instead of just finding it in print then getting the information you need and cut out all of that chit chat between it, like in the videos.like them links that were posted.

I'm pretty sure bash is backwards compatible; a 10-year-old script should, nay MUST still work on modern bash versions.

Actually, normally a Bourne cq Posix script should be working still in bash (as long as you use #!/bin/sh as it's first line).

My guess would be that bash has changed very little in it's use from a new user point of view.
The programs versus commands that one tends to use in bash could have changed a lot.
I'd get a current book on bash if you insist on learning it to be an expert user. Knowing historic usage won't help you if you need advanced tasks in that shell.

If one used bash for advanced tasks they'd need to monitor and learn changes such as found here.
https://github.com/bminor/bash/blob/master/CHANGES
You'll notice that most of the changes are not really use level changes.

With all of linux and it's programs each version and or build can be very different.

bash itself may or may not have changed much in that time but there are newer ways of doing things that many of us old UNIX ksh folks were slow to adopt.

For example using $() around a command line to use its output as input for something else instead ``.

e.g. both the following work:
list=$(ls -l |awk '{print $NF}')

list=`ls -l |awk '{print $NF}'`

But these days the first syntax is preferred and has benefits over the second (older) syntax. For one thing it is much easier to nest $() within another $() than it is to do it with ``.

P.S.
Before anyone says it: I know just "ls" will give me only the file names so I wouldn't need to do ls -l and pipe into awk - I'm just using it as an example of command line encapsulation.

Thank you all for taking your time to reply! No, I don't have plans to become an expert in bash. But you never know..

If you ever need to know how to write/form some shell command then I'd like to point out that some members at LQ seem to be pretty amazing at the task. MensaWater offers a peek.

On a related note, what are the main differences (*) between the bash version MacOS ships with (3.2 iirc), and a modern version?

(*) For a bash learner learning on MacOS, and maybe looking up things online.

from bash manpage with regards to shopts

good to know.