I LOVE bash the way it is now, and I'm having a lot of fun reading tutorials, and learning it. However, do you think that in the near future that bash will become OO?

I understand the convenience, but I really don't want it too.

I ask because not too long ago I was learning Powershell, and they are beginning to make it more OO, introducing classes, methods, and properties. Some people make the argument that Powershell should have been straight C#. I read on the MSDN blog, that powershell was designed by a group of people who all have a Unix background.

I see zero chance of this happening, but if you want a shell that's (IMHO) superior in every way including syntax, try FISH.

Powershell was designed from the beginning to interface with Microsoft's .Net framework to make system management easier. Having object oriented capabilities (I doubt that it ever will be completely object oriented) does make sense there. For Bash it doesn't. People that want object oriented system administration can do that easily with Python.

Indeed, I'm fairly sure that I read somewhere (probably MS's Hey Scripting Guy website) that PowerShell was designed to be object-orientated from the start because Windows is supposedly that way.
Since Linux isn't object-orientated I doubt BASH would go that way.

bash is written in c which usually isnt object-oriented.

You might consider getting Visual Studio for Linux and learning VB and C# instead of Bash.

Windows is not object-oriented. At least, the Win32 API was not.

How is this helpful or even relevant to the OP's question?

You seem to be on a campagin to promote C-pound-sign to GNU/Linux users, even having stated that most applications are now written in C-pound-sign and that C-pound-sign has replaced C/C++ - totally false!

Please do not pollute this forum with unhelpful and false posts not related to GNU/Linux.

2 members found this post helpful.

I have spent 33 years programming. Most front ends for applications are done in VB and the backend code is C#, VB.Net, and ASP.Net. I have played with every flavor of Linux and every version of Windows. Most programming jobs I have done is Windows. The Linux servers are mainly web servers. My wife is a web programmer. Every job she has had has been C# or VB. Limiting yourself to Linux cuts your world of opportunity by 95. I would learn to program for both worlds, if you want a job as a programmer. You will find more Microsoft than Linux in data centers.

Since your experience is almost totally Micr0$0ft product oriented and your GNU/Linux knowledge is obviously lacking, perhaps you should be participating in a Micr0$0ft oriented forum.

This site is "LinuxQuestions.org" in case you had not noticed.

I do not mean to be unkind, but LQ is known as a source for quality GNU/Linux information and most of those who participate would like to keep it that way. Incorrect and irrelevant posts degrade the overall quality of the information here and skew search results for those looking for Linux help.

2 members found this post helpful.

SCSIraidGURU, don't post if you have nothing to contribute to the topic under discussion.

1 members found this post helpful.

I would not expect a-n-y significant changes to be made to the bash shell. There's simply too much code out there which "is tied-together with bash-scripts, bailing wire, bubble gum and spit, but it works."

The good news is: you can pick any shell you want! There are lots of shells out there already, and always room for one more. The requirements that Linux/Unix has for "a shell process" are comparatively simple: I've even deployed a script as "the shell" for a (kiosk ...) user session.

You can also execute a shell-program from within your existing session. The shell-program that you execute will be aware that it is not "the shell."

[offtopic]
I have spent more than 20, and I worked at really "big" multinational companies, like for example IBM (but telecommunication related)

This is simply not true, we (almost) never used VB, C# and .Net, just unix and linux.
[/offtopic]

yes, by its nature the common command interpreter (sh?) will never be object oriented (at least I think so), that is nonsense, that should simply execute commands line by line without that overhead. If bash turned to be OO it also would be replaced by other, "simple" shell....

But as it was mentioned everyone can use python, perl or whatever he/she wants to make OO programming.

BASH is shell proramming language and atleast supports POSIX Shell specification. So it won't deviate much. For OO there are other many OO languages.

absurd question
use ruby or python or whatever, they all can be used also as 'shell'